I have 2 teams. for these teams - tasks are formed in one backlog.
then teams parse tasks in parallel sprints.
Each team has its own board, with its own filter. when a team takes a task from a common backlog, the team sets the value of its team in the team field.
question: each team has a need for its fields, screens and behavior in workflow (post-functions, validators). How can this be implemented? if you create 2 projects for each team - how to maintain a common backlog? what other possible implementations can be considered? so that there is a common backlog, but customizable working settings (screen / fields / post-functions)
Here is an approach that comes to mind. There may be other (better?) options.
I would create a different issuetype for one of the teams so that they can have a different workflow, screens etc. you could even use the issuetype to move the issues from the backlog to the other team, removing the need for the Team custom field possibly.
When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...
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