Different Screens for Issue Type 'Bug'

[Jan Szczepanski]

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.

[Nic Brough -Adaptavist-]

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:

• Bug in project A - screen 1
• Bug in project B - screen 1
• Bug in project C - screen 2
• Bug in project D - screen 2
• The impossible bit is just "Bug in project E - screen 1 and 2" because the decision on what screen to use is based on Project + Issue type.

You should read up on (or heck, just play with in a dev system) "Issue Type Screen Schemes"