To track issues related to Research and Innovation funding, we want to ensure that all issues can be "related" to a particular research/innovation initiative. One possible solution was to create a unique Issue Type for the research initiatives, then add a relationship type that specifically allows you to associate with the research initiative issue type (there would be a maximum of ten open initiatives at a time, across two different funding programs).
In concert with that, we could create a dashboard showing:
I am going to combine this with the other answer here... basically, I'll use a separate project to ensure only one user group is able to create the other issue type, and it doesn't show up in our main project Issue Type dropdown. That at least hits a couple of our points, and I can iterate from there.
I did something almost exactly like this with JIRA Server a few years ago.
We created a new issue type for Initiatives and set up an Issue Type configuration for just that issue. We then created a project (what would be a Classic project in JIRA Cloud) that was the only project in which that type of issue could be created. We locked down the permissions on that project to specific user groups to limit who could create and manage the issues there. And then we created a Link Relationship that could be used to specify the link between other issues and the Initiatives.
Here are the challenges we faced.
Our scenario was more complex also in that we had Initiatives with child Sub-Initiatives (which we created as a type of sub-task issue), and we wanted Epics linked only to the Sub-initiatives.
Another idea I had that we didn't get a chance to explore was to add a custom field of type Issue Picker to the issue that need to be linked to Initiatives. That doesn't seem to be available in JIRA Cloud OTB. It might have been something we got from an add-on. In that case, the Issue Picker field could be backed by a JQL filter to limit the issues that could be selected. If you want issues linked to only 1 Initiative, that might work for you. That could give you a simpler method for reporting rather than having to sort through Link types.
I did search for an Issue Picker field, and that would be really useful in this case if it were JQL backed. Looks like all the add-ins for that are server based so far, so that makes it a bit more difficult. I'm sure I haven't exhausted that search yet... and maybe I can find a way via API interactions and get someone on the dev team to build something?
Looks like Atlassian doesn't want to implement such a feature.
I found this add-on that is for cloud and provides a JQL backed issue picker field
Adaptavist Scriptrunner also does it, though I'm unsure if the feature is supported in the JIRA Cloud version.
You might also want to look at the Roadmap feature which lets you add the Initiative issue to the issue hierarchy, or another product for Initiative management that would integrate with JIRA. I think Atlassian has one - JIRA Align. That was just being released when I left the company where we set up the Initiative customization I described.
Hi @Yves Gagnon
Our add-on STAGIL Assets - Advanced Links could do exactly that on Jira Server/Data Center. We also have a cloud version available that has fewer features so far (due to the cloud platform restrictions) but looking at your requirements, it sounds like all of this should already be possible with the add-on on Jira Cloud.
You can also request a demo or support with the setup at https://support.stagil.com/.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events