You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hello dear community,
Is it possible to have different prefixes for particular issues assigned to one project? For instance, I want to create Service Management project, with short name ITSM, so by the default all issues will go like ITSM-1, ITSM-2 and so on. Would it be possible to set:
Incidents like SMIN-1, SMIN-2, etc
Service requests like SMRE-1, SMRE-2 etc
and so on for other issue types in this project.
Thanks in advance
Jira's prefix's are determined by the "Project Key". Each Jira project gets a "Long name" and a "Key".
If you created a single project called "Service Management" with a "key" of "ITSM", then all of your tickets will be ITSM-XXXX.
It sounds like you might be coming from the service now space, where everything is essentially a single project with different "dressings".
My recommendation would be to choose from 1 of 2 paths:
1. Create separate projects for each pre-fix, with only 1 issue type per project.
example: "Incident Management" project with a key of "SMIN", where "Incident" is your own issue type.
Then you can create a single shared screen/field/workflow/permissions configuration (as appropriate) to make management easier on yourself.
Then create a single Dashboard or Software Board with queries to aggregate all of your projects in a single view.
This option would give you the prefixes you are looking for, while still maintaining a single configuration and a single view.
2. Use a single project with the understanding that all if your "issue keys" will be ITSM-XXXX, and then use automation to pre-pend each issue type with their preferred prefix in the Issue's summary field.
ex. ITSM-1 is an incident issue type, so we would set up an automation rule to automatically apply "SMIN -" to the beginning of the summary whenever a new incident is created.
This technically does not meet your requirements for actual pre-fixes in ticket numbers, but it does meet your requirement for a single project, although I'm always puzzled why the number of projects matters to people so much.