Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Screen Organization

Court Sansom
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 14, 2019

Does anyone have any strategies, naming conventions, or addons they use to organize screens? We have just a couple of projects and a pretty simple workflow, and already the screens page in settings is getting ridiculous.

 

Ideally, I'd be able to group or filter them by project or workflow, and maybe even by a specific field's presence. This seems like a problem that's only going to get worse as we continue to customize our workflows to reflect the nuances of our business processes. Any advice would be most appreciated!

1 answer

1 accepted

1 vote
Answer accepted
Derek Fields (RightStar)
Community Champion
July 14, 2019

I completely agree that managing screens is quite weak. One of the problems is that every time you create a new project using a built-in template, Jira creates a new set of screens, even if they are identical to ones that already exist.

As a consultant, I have developed an approach that seems to work pretty well across clients:

  • I create a small number of standard transition screens that are very common
    • Assignee only
    • Resolution only
    • Comment only (no fields, just a dialog to capture a comment)
    • Worklog only (encourages entry of a worklog on a transition)
    • I name each of these with the number "1" at the front. This way when I am creating a Transition, I see these at the top of my list of transition screens
  • I delete all of the transition screens that Jira creates automatically as soon as I create a new project. This helps to keep the list to a more manageable level
  • I try to identify a standard base project, create the schemes for it and then re-use this for all new projects. If I need to customize a particular project, then I start from my base and copy the schemes as the starting point for customization. This avoids unnecessarily creating new screens when creating a new project

Hope this helps.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events