I would like to know whether it's possible to use different issue screens for on issue type.
E.g.: There is an 'QA' Department, looking for Bugs in Systems. 'QA' finds Bug in one part of the System where department 'ABC' is responsible. 'QA' creates a ticket (bug) in its own project with the bug-issue-type-screen of project 'ABC', cause project 'ABC' has got individual components, fix versions, etc.. Next time 'QA' will find another bug in a part of the system where project 'XYZ' is responsible. Project 'XYZ' has its own bug-issue-type-screen with different components....
Info: All departments using the same Bug-Workflow and the same Boards for visualizing Bugs.
No, but yes.
Screens (like many other things) are configured by project and/or issue type. You can mix and match whatever screens you want across different issue types and projects.
The one thing you can NOT do (because it's pretty much nonsense and if needed, means you've got a broken process) is have an issue type in a project have different screens because there's nothing to make the decision.
In other words you can do:
You should read up on (or heck, just play with in a dev system) "Issue Type Screen Schemes"
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs