Visual SDLC management Jira portfolio

Jira Dashboards tcan track your projects changes and team workload. 
DISCLOSURE: The date range of these samples is from a few of years ago. I have since turned my attention back to technical writing, and focussed on API.
However, having a super strong backgroung in  Jira as I do, means I  build beautiful personalized dashboard to track tickets with more acuity than just using sprint boards.

• Want a longer bulleted list of examples; go here.
• Want to see visual tech documentation examples, go here.

---

Dashboard to watch work stats and tickets move through the sprint  (click images to enlarge)

---

Dashboard to watch ticket progress  (click images to enlarge)

Dashboard to watch work log and ticket updates  (click images to enlarge)

---

Engineering Workflow examples (click images to enlarge)

---

---

​(Note: the content may not match your system, but the principles are here)
Links:

• My tutorial Jira 101, and Jira tutorial level 102
• My cloning tickets script and instructions
• My How to design a Jira dashboard
• https://my.atlassian.com
• https://confluence.atlassian.com
• https://support.atlassian.com
• https://marketplace.atlassian.com
• https://bitbucket.org/
• Atlassian documentation link
  • Jira Cloud-specific documentation
  • Jira filter documentation link
• JQL Advanced searching - Fields Reference
• JQL Advanced Searching - Operators Reference
• JQL Advanced Searching - Functions
• Comment syntax rules
• Atlassian documentation Portfolio for Jira:
  • ​Great Jira Portfolio how-to video–2014
  • On demand webinar–2018

---

How To Customize Order of Transition options
When viewing an issue, most of the operations and workflow transitions are available from a row of buttons at the top of the issue.

To change the number of transition buttons from the default of two:

By default, the first two transitions appear as separate buttons in the set of transition buttons. Additional transitions appear in the Workflow menu. The order in which these buttons appear is based on the order defined in the system workflow.

1. Shutdown JIRA.
2. Edit the jira-config.properties file in your JIRA Home Directory. See Making changes to the jira-config.properties file for more information.
3. Change the value of 'X' in the ops.bar.group.size.opsbar-transitions = X property of this file to be the number of transition buttons required before the Workflow menu.
    If this property does not exist in your jira-config.properties file, add it. Otherwise, a default value of 2 is assumed.
4. Save the updated jira-config.properties file.
5. Restart JIRA. 

To change the order of transition buttons:

To change the order of transition buttons, including additional transitions in the Workflow menu, add the property key opsbar-sequence to each workflow transition that you wish to reorder. Each opsbar-sequence property key requires a property value that defines the order of the transition action on issue views.

1. Go to the transition's properties, as described in Transition properties above.
2. Type opsbar-sequence into the Property Key field, under 'Add New Property'.
3. Type a value In the Property Value field, The value must be a positive integer (starting at '0'); it defines the order of the transition buttons on issue views.
   Consider using a sequence of opsbar-sequence property values like 10, 20, 30... to allow new transitions to be easily added later.
4. Click Add.

 

More info: Workflow Properties Link

---

Label Filter: Label is not EMPTY AND due >= startOfWeek() AND due < endOfWeek(1) AND status in (closed, resolved) 
created >= 2014-01-01 AND created <= 2014-03-01