Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Same project, but deferent Issue numbering format. like ABC-1, and CDE-1 in same project.

Hi, I have a requirement, could you please help in setting up.

I want a department that deals with 3 different clients, e.g. ABC, DEF, GHI.

Now while raising issues selecting the project will be tough, so rather in same project we have added a custom field for client, that holds these options ABC, DEF and GHI. But the issue number is not getting controlled by this selection and it is like XYZ-1, XYZ-2 and XYZ-3. But we actually wanted ABC-1, DEF-2 and GHI-3.


Could we do this?

Thank you


2 answers

2 accepted

2 votes
Answer accepted
John Funk Community Leader Jan 05, 2021

Hi Manas - no, you will not be able to do that unless you create separate projects for each one. Since you have a custom field that captures the different clients, you have to know those to be able to populate that field - which would create the different keys as you describe - ABC-1, DEF-2, etc. So, if you know them then, you should be able to create them as separate projects and create the new issue in the appropriate project. 

The other option is to create a simple JSM project with a portal up front to capture the initial request. And then when the custom field is updated for the client, create an automation rule that clones the issue (or creates the issue from scratch) in the appropriate Classic Software project. We do that in several cases in our organization. 

Dirk Ronsmans Community Leader Jan 05, 2021

Perhaps not really a solution to your issue but have you thought about the fact that it makes more sense that you define the issue key prefix?

If you have issues from multiple clients they can surely use the same project but imho the provider providing the support should define what the key is.

An alternative could be to just add that custom field/client name in your summary through an automation as a prefix there?

If you however take @John Funk 's route you can consider using the Queues for JIRA plugin. It allows you to create multi project queues so you don't have to jump from project to project to handle the issues :)

Thanks @John Funk  and @Dirk Ronsmans for the answers and opinions.

I liked/prefer both the ideas. Have to try both of them to get a feasibility idea.

Like John Funk likes this
0 votes
Answer accepted

Hi @Manas Sinha ,

It's not possible in jira project. 

You can create 3 different projects with these keys and create a board and configure with these 3 project issues. This will help to see all issues in single place.

this make sense... I will give a try of this approach. Thank you @Kagithala Babu Anvesh 

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

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

7,104 views 8 28
Join discussion

Community Events

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

Events near you