We are going to add cross-projects components list to Jira (Cloud) by adding a global custom field. This raises the additional question of whether there is a possibility to define project based on the custom field value? It doesn't seem to be, but maybe I missed something, like post-function, add-on, etc.?
Why you can not let a user choose from the project field? Or an issue could be created in multiple projects if you choose a value from the custom field?
If a value from the custom field corresponds striclty to a single project then the custom field is redundant.
Hi @Alexey Matveev,
The reason why we don't want to do it, because most of the users have no idea what project the component belongs to. In this way, using the global list of components, we want to enable any user to create a ticket and address it to the correct project. NB! The default category field should be preserved and the additional custom field should be used on top.
I would consider moving to Jira Service Desk. I think it would help you with your requirements. You can define as many request types as you want there (that would be the components) and connect them to certain issuetypes and certain customfield values. It will be one project but the user does not have to know about internals of the project.
I've had this request recently as part of a project, and the only answer we could get to was "create all issues in a dummy project and then write a horribly complex automatic move-issue-automatically" process. We went with Service Desk instead, as it simplifies things for the users so they don't need to know the project.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot