nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can I show the same issue in two different projects?

Fernando Claros

We have a project in which our customer create bugs and feature requests.

Our team is working in another project where we have our own features and our internal private information.

Is there a way to show the bugs entered by our customer in our main development project? We don't want to copy them, to avoid overhead. Instead, we would need them to be the same issues, so our customer sees them change as our team works on them. Moreover, if our customer enters a comment we would need our team to see that in their side.

Any help would be greatly appreciated!

Accepted answers

Nic Brough -Adaptavist-

You can't.

An issue belongs to a single project. That's it.

You could start trying to do things with links, displays and crossovers, but that needs some coding. Even duplicating (which you'd prefer to avoid) requires some coding.

For your needs though, I'd take a different approach and use permissions. You have one project. The permission scheme for "browse" should say "Our developers, reporter-only and nominated people". This is how Atlassian handle their Support project - they can see it all, the people who report an issue can see ONLY the issues they report and there's a function to include other people.

The reporter-only trick is important though - you can't just say "reporter" in an off-the-shelf Jira, you need to enable an extra function. See https://confluence.atlassian.com/display/JIRA/Current+Reporter+Browse+Project+Permission

All comments

Nic Brough -Adaptavist-

You can't.

An issue belongs to a single project. That's it.

You could start trying to do things with links, displays and crossovers, but that needs some coding. Even duplicating (which you'd prefer to avoid) requires some coding.

Robert Dibley

issue queries are not limited to a single project - the only problem is if you rely on something which doesn't exist in one of the projects, which can easily happen if you customise a lot, but doing a multi-project query is easy enough, even using the basic interface. So, although you would not actually be seeing the issue in another project, you could have it in a query tailored to your teams requirements.

Nic Brough -Adaptavist-

Yes, my apologies, I didn't even mention reporting. When you say "show an issue in two different projects", you can't have the issue in two places, but there's absolutely nothing to stop you reporting on it across projects.

Fernando Claros

Thanks a lot, Nic! You have been really helpful

Fernando Claros

Thanks for pointing this out Robert! Your remark is very relevant in our context

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration