show environment status in linked issues

Right now, we show the pipeline and MR status in an issue that is linked to/from a MR. I propose we do the same with environments, so you can see whether a certain change / issue is live somewhere.

cc @markpundsack @ayufan @victorwu

added ~874211 label

@JobV Do you envision this in a system information box, like we do for MRs, or something more subtle, like in the Related Merge Requests list, just adding content/link after the merge requests?

One concern is that there can be multiple MRs, so we'd have to extend the info box to handle that, if we went that direction. Probably easy to do since it's just more lines. But we don't have the system information box on issues at all currently.

/cc @dimitrieh

@markpundsack I imagine a very minimal version of something like the MR box. Probably with less information, but having some buttons to quickly check something out would be very cool.

I'm sure @dimitrieh has some ideas.

The interplay between issues and MRs is less than optimal. Several times I've looked at an issue, and even asked if there's any update, only to have someone point out that there's an MR already, and it's almost done. Partially, I'm used to GitHub where, using hub CLI, we'd usually convert issues into pull requests rather than link between them.

@markpundsack a more direct coupling is definitely something to consider. We already encourage this with the "Create branch" button in an issue. Should we do more?

Related: In issue boards, I've often wanted to know if there is a related MR already, so I imagine showing the MR number right on the issue card somewhere. I could then see adding an icon to visit the review app for that MR, all from the issue board. That might be going to far though.

added feature proposal ~14281 labels

I don't think that's too far @markpundsack, that sounds amazing. And then imagine having a filter for issues with/without MRs, review apps, etc. Super cool.

@victorwu can you follow up / close here?

Let's work on related issues first. Closing for now.

closed

@victorwu looking back at this issue, I think this is still something that might be interesting. I still want to be able to see what is live where. No need to do this now, but not to close, I'd say.

reopened

changed milestone to %Next 3-6 months

moved to gitlab#8452

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