You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2010/10/06 02:41:32 UTC

[jira] Closed: (INFRA-2494) Additions to Traffic Server Jira workflow

     [ https://issues.apache.org/jira/browse/INFRA-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gavin closed INFRA-2494.
------------------------

    Resolution: Fixed
      Assignee:     (was: Gavin)

Both Done.

You now have a 'Provide Patch' workflow which when someone has provided patch, can click on.

You now have a 'Backport to Version' field, which at any time during an issue, you can select one or more versions for backport.

HTH

> Additions to Traffic Server Jira workflow
> -----------------------------------------
>
>                 Key: INFRA-2494
>                 URL: https://issues.apache.org/jira/browse/INFRA-2494
>             Project: Infrastructure
>          Issue Type: Wish
>      Security Level: public(Regular issues) 
>          Components: JIRA
>            Reporter: Leif Hedstrom
>            Priority: Minor
>
> The Traffic Server project would like to extend, if possible, the workflow for our Jira bugs. In particular, we would like to have the additional 'states' of a) Bug is being worked on (this would happen after bug is assigned)   and b) Proposed patch needs a review. To quote Miles Libbey, the workflow then would be something like
> 1) Ticket opened
> 2) Ticket Assigned to a developer
> 3) Ticket is worked on -- move to "in progress"
> 4) Submit patch, request code review
> [repeat steps 3-4 as needed]
> 5) Code is accepted, and committed.  Ticket marked fixed. 
> (The current workflow has only step 1, 2 and 5).
> Thanks!
> - Leif

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.