You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2010/02/16 05:00:27 UTC
[jira] Created: (INFRA-2494) Additions to Traffic Server Jira
workflow
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.
[jira] Commented: (INFRA-2494) Additions to Traffic Server Jira
workflow
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853126#action_12853126 ]
Gavin commented on INFRA-2494:
------------------------------
Take a look at the OFBIZ jira workflow, I added a 'Submit Patch/Patch Available' workflow to theirs.
Note that the Patch should be able to be added a 'open/re-open' not just after 'in progress' , I'd say.
Let me know if that works for you and I'll do the same.
> 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.
[jira] Commented: (INFRA-2494) Additions to Traffic Server Jira
workflow
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860685#action_12860685 ]
Leif Hedstrom commented on INFRA-2494:
--------------------------------------
Gavin: Sounds good to me. I'm wondering, would it also make sense to have a workflow for "Request for backport", which would also take one (or more) branch versions? That'd be a useful addition for us, since we use a slightly modified variant of HTTPD's voting on trunk bugs to be backported to various release branches.
Thanks!
-- Leif
> 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.
[jira] Commented: (INFRA-2494) Additions to Traffic Server Jira
workflow
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834076#action_12834076 ]
Leif Hedstrom commented on INFRA-2494:
--------------------------------------
Gavin educated me on the "Start progress" / "Stop progress" workflow steps, that's adequate for step #3 in this request.
> 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.
[jira] Assigned: (INFRA-2494) Additions to Traffic Server Jira
workflow
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin reassigned INFRA-2494:
----------------------------
Assignee: Gavin
> 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
> Assignee: Gavin
> 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.
[jira] Closed: (INFRA-2494) Additions to Traffic Server Jira
workflow
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ 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.