infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Commented] (INFRA-17528) JIRA Workflow Changes
Date Wed, 23 Jan 2019 13:09:00 GMT


Benedict commented on INFRA-17528:

I've completed a first pass at making the changes, modulo the three fields we would ideally
have an external plugin for, and without the dynamic field population that would also benefit
from a plugin.  The two plugins we would ideally get ahold of are:

Alternatively, there are some apps that permit fetching options for a list from a URL, which
we could point to gitbox or GitHub.  I don't fully understand how the open source licensing
works for Atlassian Marketplace.

>From our perspective, we would prefer to proceed with the initial changes and follow up
with the extra fields when they are available, unless we think it will be easy to arrange
a license.

I will be posting to the community mailing list later today to ask for people to quickly test
the changes to the test Jira instance, to minimise the number of round trips we'll end up
needing, so hopefully in a few days we'll be sure it's good to go.  Though no doubt there
will be some tweaking with the extent of the changes I have made.

I tried to keep a log as I went, at least for everything that was not directly workflow related,
which I replicate here.  Some of these changes I can make, and most of them should be imported
alongside the workflows, but some will I think need to be replicated by you on the production

* Migrate reviewer to reviewers: 
** Export reviewer, reviewers fields to CSV (I will replicate)
** Import as reviewers to update any issue where it is empty (Needs to be done by Jira admin)
* Priorities
** Create new “Default Project Priority Scheme” priority scheme, that duplicates the Jira
Default (because otherwise all projects will inherit our new priority labels)
** Associate all projects with it (this takes several minutes)
** Add: Urgent (Red, Blocker img), High (Orange, Critical img), Normal (Green, Major img),
Low (Blue, Minor img)
** Add: “Cassandra Priority Scheme” 
*** With values: Urgent, High, Normal, Low
*** With default: Normal
*** Associate with Cassandra project
**** Trivial, Minor => Low
**** Critical, Blocker => Urgent
**** Major => Normal
* Statuses
** Add: Triage, Review in Progress and Change Requested, Requires Testing
* Move all ‘Reopened’ issues to ‘Open’ (I can replicate)
** via ‘Submit Patch’ and ‘Cancel Patch’
** using a label ‘remove-reopen’
* Add Fields
** Severity: Select List (Single) [Low, Normal, Critical]
** Complexity: Select List (Single) [Low Hanging Fruit, Normal, Challenging, Byzantine, Impossible]
** Discovered By: Select List (Single) [User Report, Code Inspection, New Unit Test, Existing
Unit Test, Performance Regression Testing, Fuzz Testing, Workload Replay Testing, Shadow Traffic,
Adhoc Testing]
** Bug Category (see wiki page)
** Test and Documentation Plan: Multi-line text
* Screens (Should be imported)
** Create new Screens
** Create new Screen Schemes for Bug and Default
* Create new Workflows (too complex to list), including required field validations, statuses,
transitions etc. (Should be imported)
* Create Apache Cassandra Default Issue Type Scheme (Should hopefully come with import?)
** Copy Apache Default
** Remove Wish and Test
** Associate with Cassandra
*** Move Wish and Test to Improvement

> JIRA Workflow Changes
> ---------------------
>                 Key: INFRA-17528
>                 URL:
>             Project: Infrastructure
>          Issue Type: Task
>          Components: JIRA
>            Reporter: Benedict
>            Assignee: Gavin
>            Priority: Major
> Recently the Cassandra development community [discussed|]
and [voted|]
to overhaul its JIRA schema and workflow to better match the reality of how the project uses
it.  Unfortunately very few of the changes can be achieved autonomously.
> A document describing the desired changes [lives on our wiki|].
> There are a number of facets to this that we will need your assistance and input to achieve:
> * Adding, modifying and removing a number of fields
> ** Some of these fields are hoped to be multi-select lists that can be modified autonomously
by the project, which looks to require a plugin - is there an ASF policy on JIRA plugins?
> ** Some of these fields will only be displayed for certain issue types
> ** Priority options need to be modified
> * Removal of issue types Wish and Test
> * Introduction of new issue states: Triage, Review in Progress, Change Requested
> * Introduction of new transition screens with required fields to complete the transition
> * Removal of contributor role, with Jira-users being permitted to do anything they were
previously permitted
> Basically we need to move away from the Default Screen, Default Priorities, default everything.
 We will also need extensive modifications to our custom workflow.
> We understand this is a fairly significant burden, and would like to take ownership of
as much as possible.  If it is workable to assign us the permissions to make these edits ourselves,
we would be happy to do so.  Presently, the only change I seem able to make autonomously is
the introduction of the new Component options that we voted on.

This message was sent by Atlassian JIRA

View raw message