www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jake Farrell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-7181) JIRA project configuration changes for AURORA
Date Sat, 11 Jan 2014 01:15:53 GMT

    [ https://issues.apache.org/jira/browse/INFRA-7181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868570#comment-13868570
] 

Jake Farrell commented on INFRA-7181:
-------------------------------------

- Reviewable status added
- Issue type schema set, existing tickets ported

> JIRA project configuration changes for AURORA
> ---------------------------------------------
>
>                 Key: INFRA-7181
>                 URL: https://issues.apache.org/jira/browse/INFRA-7181
>             Project: Infrastructure
>          Issue Type: Task
>          Components: JIRA
>            Reporter: Chris Lambert
>
> Before we can migrate our backlog to Apache's JIRA instance, we'd like a few project
modifications to more closely match our workflow.  Once this is done, we'll provide an XML
dump of tickets (in a separate INFRA ticket) for import into the project.
> # Notifications:
> ## Create an {{issues@aurora.incubator.apache.org}} email list, and send all (or some
subset of all) notifications there
> ## Enable adding watchers to a ticket (very common in our workflow)
> # Workflow changes:
> ## New status:  Reviewable
> ## Start using the Mesos Workflow; if we need modifications, we can copy it and go fro
there
> ## We'd like the standard Epic issueType workflow for Greenhopper
> # Issue Types:
> ## Add and remove issue types
> ##*     Epic  (see Greenhopper)
> ##*     Bug
> ##*     Story  DEFAULT
> ##*     Task
> ##*     Triage
> ##*     Sub-task
> ## For existing tickets, you can use this mapping to the new types
> ##*     Bug -> Bug
> ##*     Improvement -> Story
> ##*     New Feature -> Story
> ##*     Task -> Task
> ##*     Test -> Task
> ##*     Wish -> Story
> ##*     Sub-task -> Sub-task
> Bonus:
> # Would Apache consider creating a "neutral" issue priority, such as "Unpriorizied"?
 Typically we like to hold off making an assessment (such as "Major" or "Minor") until after
tickets have been reviewed, to reduce the noise that is often found in the priority field.
 A field like this set to the default for our project would be nice.  But IIUC, priority is
a global field, so there may be pushback to making such a sweeping change.
> Thanks in advance,
> Chris
> /cc [~wfarner], [~jfarrell], [~davelester], [~njm]



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message