Skip to main content

Jira Administration

Some things I have setup in Jira to make life better for me, with the way we work.


Use Case 1: You should not close a story when sub tasks are not complete

How?

Jira - Workflow - Edit Transition

Condition, before allowing a story to Status Category Done

"All sub-tasks must have one of the following statuses to allow parent issue transitions:" (All done statuses)


Use Case 2: You should not close a story until the blocker or impediment is resolved.

How?

Jira - Workflow - Edit Transition

Condition, before allowing a story to Status Category Done

"Value Field"

The field Flagged will have to be not equal to value '"Impediment"'. Compared as String.


Use Case 3: Set resolution when completing an item.

Why? If no resolution is set some reports and metrics don't calculate correctly.

How?

Jira - Workflow - Edit Transition

Done

Post Function, Status Category = Done

JMWE The value(s) of field Resolution of the current issue will be set to Done (unless the field already has a value). Run as add-on user.

The Epic Status of the issue will be set to Done.

OR

Jira - Workflow - Edit Transition

Will not do (abandoned, not needed, etc.)

Post Function, Status Category = Rejected

JMWE The value(s) of field Resolution of the current issue will be set to Won't Do (unless the field already has a value). Send notification. Run as add-on user.

The Epic Status of the issue will be set to Done.

Use Case 4: Copy settings for sub-tasks that should match parents to save time

Post Function, Status Category = As many as possible

JMWE "Copy field value from parent issue (JMWE add-on)"

  1. The value(s) of field Assignee will be set from the issue's parent Assignee field (unless the field already has a value). Send notification. Run as add-on user.
  2. The value(s) of field Team Name will be set from the issue's parent Team Name field (replacing existing values). Run as add-on user.
  3. The value(s) of field Deliverable will be set from the issue's parent Deliverable field (replacing existing values). Run as add-on user.
  4. The value(s) of field Planned Quarter will be set from the issue's parent Planned Quarter field (replacing existing values). Run as add-on user.

Comments