Make more visible when an issue was moved.

Description

When an issue is moved between project by a team lead, often the reporter only noticed that the issue was closed. And the first reaction is not to scroll down the issue history to find out if the issue was moved.

UPDATE: As expected, 30 minutes later, the user re-open the moved issue

Proposal

I would recommend that when an issue is moved, to indicate it directly bellow the CLOSED status.

Warning on the text input field.

moved to example/123

Other ideas:

Sorry, only have mspaint ! Add a text line bellow ?

Links / references

Documentation blurb

When an issue has been moved to an other project, it will be clearly indicated bellow the statu a of the issue. This will help collaborators who open the closed issue to get quickly to the new up to date issue.

@Sadortun Thanks for the feedback. This is already being discussed in the following issue:

• https://gitlab.com/gitlab-org/gitlab-ce/issues/31223

We have opened the implementation for a Community Contribution. Please could you transfer your feedback to that issue so that we can keep the discussion all in the once place?

Closing this issue in favour of the original

closed

mentioned in issue #31223 (moved)

@markglenfletcher Thanks for pointing out. I did not find it when i search for an existing issue. Feedback added

reopened

Reopening because of https://gitlab.com/gitlab-org/gitlab-ce/issues/31223#note_28765043

Thanks @Sadortun! Some good ideas here.

@hazelyang Can you take a look? I don't think we should change the closed status up top to Moved because it wouldn't map to our available tabs when searching. But we could include some UI that shows the issue was moved. Also in the comment box, like Sam included, with a link to the new issue. I'm not sure it needs to be our error red color. This issue has been moved to [project#123].

Confidential example:

Also note Sam's suggestion when trying to reopen a moved issue:

When trying to re-open a close issue

I dont know if it should be a separate issue, but a warning should be displayed when we try to re-open a MOVED issue

@tauriedavis @Sadortun

Also in the comment box, like Sam included, with a link to the new issue. I'm not sure it needs to be our error red color.

I think people can notice the message easily, even though it's not red color.

When trying to re-open a close issue

I dont know if it should be a separate issue, but a warning should be displayed when we try to re-open a MOVED issue

My thought:

Has a message bar below the issue header. It's obvious and close to "Reopen issue" button.

Thanks @hazelyang!

How should the note: This issue has been moved to ... be positioned in the note form when the issue is confidential ?

I think we should favor #31223 (moved) before this issue. The main question is:

• Should it be allowed to re-open the 'origin' of a moved issue ?
• Should it be allowed to comment a closed issue that was moved ?

In my opinion, it should not be possible to make those actions on the moved issues at all.

moved to gitlab#9521

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