If am using 2 boards under one similar project with the same workflow.
how can i differentiate the issue Id?
What you want to differentiate when you say issue id
If you are using 2 board under same project with same filter then sprint which present in the one board then same sprint will be visible on another board. and those board will be in synch
refer this
Thanks,
Sachin
Hi Utteja,
The issue id (known as the issue Key in Jira) is the unique identifier for the issue. Therefore, it cannot be displayed as different values in different places - it must always be the same value for integrity sake.
You can have other data appear on the card that is different on each board - why would you need the key of the issue to appear differently on different boards?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The issue id (known as the issue Key in Jira) is the unique identifier for the issue. Therefore, it cannot be displayed as different values in different places - it must always be the same value for integrity sake. - i agree with it
why would you need the key of the issue to appear differently on different boards?
Two teams are working under one project with the unified workflow they want two boards under one project with same configurations, but they want to differentiate with the key to the issue to appear differently on different boards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What kind of differentiation you want among issues? What is your goal? E.g. to know that an issue AAA is displayed on "board a", while issue BBB is displayed on "board b"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
for example, project has an issue as A-45
in board-A it can be A-45 but in the board- B can we change the issue ID as B-45?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If these issues are located in the same project, then they will have the same issue key. In order to have a different issue key, you have to create them in a different container (jira project).
What you can do, if you want to have a sort of differentiation among your issues is to create a custom field with two distinct values, e.g. "boardA", "boardB". Then you should create an automation which will set the value of this field to boardA or boardB, based on certain criteria, e.g. if the issue type is story and has the value of that field to be equal to 0, and it is assgined to a specific user etc. Usually, the criteria should much those of the filters' JQLs.
If you want to separate the issues based on which team is working on each issue, simply use the component functionality https://support.atlassian.com/jira-software-cloud/docs/organize-work-with-components/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Utteja Ragni Sai Shree V ,
boards are based on a filter. Please edit your board filter in order to setup what issues need to be retrieved and showed on your board. Please, keep in mind that a board could show issues from different projects.
Fabio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I agree with your sentence but here I am referring it with the only one project with different boards. To add the filter the project code will be same. To differentiate the issue id what can I do.
so that's my Question.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can base your filter to different fields. If your filter is based on issue key you can use :
issuekey in ("AAA-1","AAA-2"...)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.