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, 20 Feb 2019 10:26:00 GMT


Benedict commented on INFRA-17528:

bq.  Import as reviewers to update any issue where it is empty (Needs to be done by Jira admin)

I've uploaded a csv file for you to use for this step.  It contains the Key, Summary and Reviewer
field for all tickets where Reviewer is not empty and Reviewers is empty.  The CSV import
tool permits you to update existing issues, so long as you specify the Key and Summary of
those issues.

> JIRA Workflow Changes
> ---------------------
>                 Key: INFRA-17528
>                 URL:
>             Project: Infrastructure
>          Issue Type: Task
>          Components: JIRA
>            Reporter: Benedict
>            Assignee: Gavin
>            Priority: Major
>         Attachments: update_reviewers.csv
> 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