You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Jake Farrell (JIRA)" <ji...@apache.org> on 2014/07/24 04:15:40 UTC

[jira] [Commented] (INFRA-8074) Are projects allowed to define a workflow other than the default agile workflow in Apache jira?

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

Jake Farrell commented on INFRA-8074:
-------------------------------------

It is possible to define workflows, which project this is for?

> 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
>
> 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)