www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tony Stevenson (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (INFRA-8074) Are projects allowed to define a workflow other than the default agile workflow in Apache jira?
Date Sat, 02 Aug 2014 11:41:12 GMT

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

Tony Stevenson resolved INFRA-8074.
-----------------------------------

    Resolution: Fixed

> Are projects allowed to define a workflow other than the default agile workflow in Apache
jira?
> -----------------------------------------------------------------------------------------------
>
>                 Key: INFRA-8074
>                 URL: https://issues.apache.org/jira/browse/INFRA-8074
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: JIRA
>            Reporter: John Francis Unson
>            Assignee: Tony Stevenson
>         Attachments: Workflow.pdf
>
>
> Are projects here in Apache Jira allowed to define a workflow other than the default
agile workflow?  if yes, I'd like a Blocked status and an In Review status introduced to our
workflow.
> If yes, then I'd like to have the following flows added:
> - Anything can go to Blocked status and vice versa (e.g., open to blocked, blocked to
open, blocked to in progress, etc.), with the exception of Closed.
> -- Blocked status can go to anything, including Closed, but not the other way around.
> - In Progress items can go to In Review, and vice versa.  
> - In Review can go to Resolved or Closed, and vice versa.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message