Set Project based on Custom field value

Hi,

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.?

Any ideas?

2 answers

0 vote

Hello,

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.

Alexey Matveev Community Champion Nov 01, 2017

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.

@Alexey Matveev Thanks for advice, this might be an option if we did not have to adhere to the current structure, but at the moment we need to use different existing projects.

If any ideas how could this be solved in the current conditions?

Alexey Matveev Community Champion Nov 01, 2017

@Valeriia Iuzhakova

All solutions I can see are akward and would require too complicated customizations which would be difficult to mantain.

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.

@Alexey Matveev@Nic Brough [Adaptavist] thank you for the advices, I found it really helpful for decision-making!

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,321 views 14 20
Join discussion

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot