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; } } }

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

Manas Sinha

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

-Manas

Accepted answers

KAGITHALA BABU ANVESH_z1zl10

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.

John Funk

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.

All comments

KAGITHALA BABU ANVESH_z1zl10

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.

John Funk

Dirk Ronsmans

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

Manas Sinha

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.

Manas Sinha

this make sense... I will give a try of this approach. Thank you @KAGITHALA BABU ANVESH