www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davor Bonaci (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-12698) New JIRA workflow for certain Apache Beam issues
Date Tue, 04 Oct 2016 06:53:20 GMT

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

Davor Bonaci updated INFRA-12698:
---------------------------------
    Description: 
We've been asked by some members of the Apache Beam community to develop a process to better
track pending Proposals, which are larger pieces of work benefiting from a community-wide
discussion.

I think their request is best solved with a separate Issue Type in JIRA and corresponding
Workflow.

To try to address this request, would it be possible to create new Issue Type called "Proposal",
with the following Workflow:

Initial State: Idea
"Propose Design" --> "Under Discussion"
"Abandon" --> "Abandoned"

State: Under Discussion
"Approved by community" --> "In Implementation"
"Pause discussion" --> "Idea"
"Abandon" --> "Abandoned"

State: In Implementation
"Complete" --> "Completed"; "Fix Versions" field mandatory in this transition.
"Abandon" --> "Abandoned"
"Needs more discussion" --> "Under Discussion"

Terminal State: Completed
"Reopen" --> "In Implementation"

Terminal Stated: Abandoned
"Reopen" --> "Idea"

Thanks!

  was:
We've been asked by some members of the Apache Beam community to develop a process to better
track pending Proposals, which are larger pieces of work benefiting from a community-wide
discussion.

I think their request is best solved with a separate Issue Type in JIRA and corresponding
Workflow.

To try to address this request, would it be possible to create new Issue Type called "Proposal",
with the following Workflow:

Initial State: Idea
"Propose Design" --> "Under Discussion"
"Abandon" --> "Abandoned"

State: Under Discussion
"Approved by community" --> "In Implementation"
"Pause discussion" --> "Idea"
"Abandon" --> "Abandoned"

State: In Implementation
"Complete" --> "Completed"
"Abandon" --> "Abandoned"
"Needs more discussion" --> "Under Discussion"

Terminal State: Completed
"Reopen" --> "In Implementation"

Terminal Stated: Abandoned
"Reopen" --> "Idea"

Thanks!


> New JIRA workflow for certain Apache Beam issues
> ------------------------------------------------
>
>                 Key: INFRA-12698
>                 URL: https://issues.apache.org/jira/browse/INFRA-12698
>             Project: Infrastructure
>          Issue Type: Task
>          Components: JIRA
>            Reporter: Davor Bonaci
>
> We've been asked by some members of the Apache Beam community to develop a process to
better track pending Proposals, which are larger pieces of work benefiting from a community-wide
discussion.
> I think their request is best solved with a separate Issue Type in JIRA and corresponding
Workflow.
> To try to address this request, would it be possible to create new Issue Type called
"Proposal", with the following Workflow:
> Initial State: Idea
> "Propose Design" --> "Under Discussion"
> "Abandon" --> "Abandoned"
> State: Under Discussion
> "Approved by community" --> "In Implementation"
> "Pause discussion" --> "Idea"
> "Abandon" --> "Abandoned"
> State: In Implementation
> "Complete" --> "Completed"; "Fix Versions" field mandatory in this transition.
> "Abandon" --> "Abandoned"
> "Needs more discussion" --> "Under Discussion"
> Terminal State: Completed
> "Reopen" --> "In Implementation"
> Terminal Stated: Abandoned
> "Reopen" --> "Idea"
> Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message