Include field `iid` when adding an issue

It would be very useful if we could include the iid field when creating an issue, mainly due to migration from other repositories to Gitlab.

Motivation

A repo imported from other host loose references to issues.

Example

Let's say I have a project hosted in Github and I decide to migrate to Gitlab. There, I already have my Git history referencing issues by number.

When I migrate this project from Github to Gitlab, I completely loose this reference, because issues will gain a new number (aka iid). Far worst, issue numbers will get confusing due to this renumbering. So, an existing commit or note, will reference the wrong issue.

The same applies when I migrate from gitlab.com to a self hosted solution.

Solution

The New Issue API should include the iid field, which would be populated with the Github issue number to keep references.

Note: the iid field should only be available through API and is optional.

Problems and concerns

• Trying to create an issue with an existing iid: API must return error.
• The new iid is greater than the last issue_id in the current repo: API must adjust the "last iid" to the new created iid.

Title changed from Include field iid when adding an issue to Include field issue_id when adding an issue

@DouweM Please review this

Sounds OK to me, although it would be called iid rather than issue_id.

Thank you @kelvinmutuma and @DouweM

I wrote issue_id because it's in Single Issue and [Edit issue] (https://gitlab.com/help/api/issues.md#edit-issue) APIs.

The List issues API uses uuid. :-/

It would be nice if these docs were updated to refer only to issue_id or iid, what is the official one.

@viniciusban issue_id is the global ID across all projects, iid is the ID within the current project. I think it's consistent.

Title changed from Include field issue_id when adding an issue to Include field iid when adding an issue

Absolutely right, @DouweM

I've just edited the issue to correct that mistake.

Thank you, again.

Added ~874211 label

@DouweM Accepting Merge Requests for this one?

added Accepting Merge Requests label

mentioned in commit 6cccf59c

moved to gitlab#3744

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue

mentioned in merge request !14785