I am very new to Jira. this is my first post .
How can the parent key be changed to B or C ... instead of just A1, A2 A3 etc. If this is possible then will the child task also inherit the parent naming of A1 or B1 or C1 and sub task as A1-1 or B1-1 ... etc
Hi @Sanjay A1 is the project key and the number you see after hyphen that is unique I’d Auto generated by Jira when you create a Work item eg. epic, story etc.
the project key stays the same, but the issue number auto-increments for every new issue.
Hello Chandra, Thanks for your reply. Can the unique id for the work item in the epics can be changed to match the id of the epics. I do not wish it to be auto generated.
The unique id of the work item should ideally match the id or alphabet of the epic.
Thank you
Sanjay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, you can’t change Jira issue IDs they are auto-generated in Jira.
If you would like to assign custom number. Use a custom text field to store/match the Epic ID instead.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the community!
The A1 is the key of the space, which means it is the unique identifier. It is not related to the work type, but instead is the unique identifier of the work item within the space.
If you change it, it will be changed across all work items within the project. You can learn how to do it by reading this documentation:
https://support.atlassian.com/jira-cloud-administration/docs/edit-a-projects-details/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Sanjay ,
A1,B1,C1 is the key of your project/space and it is the same for all items within space.
Hope this clarifies,
Fabio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Sanjay ,
You can’t change existing issue keys, but you can change the project key (which only affects future issues), or move issues to another project, where they’ll get new keys automatically.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.