Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Fix Version/s: Initial Clearing
    • Component/s: JIRA
    • Labels:
      None

      Description

      As a project administrator, I need the ability to move a ticket between states for Greenhopper to work correctly. Specifically, I'd like to be able to drag tickets between columns on my [Rapid Board|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=1].

      I don't know if the easiest way is just to modify our existing workflow, or if there are other GH configurations that we'd benefit from in moving to whatever standard GH settings are recommended. Thoughts?

        Activity

        Hide
        Mark Thomas added a comment -
        Done.
        Show
        Mark Thomas added a comment - Done.
        Hide
        Chris Lambert added a comment -
        Can you add role Administrator?
        Show
        Chris Lambert added a comment - Can you add role Administrator?
        Hide
        Mark Thomas added a comment -
        Mesos now has a custom workflow that permits any user with the developer, contributor or committer role to stop progress on a task.
        Show
        Mark Thomas added a comment - Mesos now has a custom workflow that permits any user with the developer, contributor or committer role to stop progress on a task.
        Hide
        Chris Lambert added a comment -
        Unfortunately, no. Specifically, I want to be able to transition any ticket from "In Progress" back to "Open". I can do this if I am the assignee; I can't do this if I'm not the assignee.

        The use case I'm trying to satisfy is that tickets often get started but not completed, or preempted by other work, so I want to be able to move things around as the project manager.

        I think this is an issue with the transitions in the workflow... seems like the transition already exists because I can do it as the assignee... but it's just not available to me if I'm not the assignee.
        Show
        Chris Lambert added a comment - Unfortunately, no. Specifically, I want to be able to transition any ticket from "In Progress" back to "Open". I can do this if I am the assignee; I can't do this if I'm not the assignee. The use case I'm trying to satisfy is that tickets often get started but not completed, or preempted by other work, so I want to be able to move things around as the project manager. I think this is an issue with the transitions in the workflow... seems like the transition already exists because I can do it as the assignee... but it's just not available to me if I'm not the assignee.
        Hide
        Tony Stevenson added a comment -
        Chris,

        Please see this attachment - you will see the far right of the image is the context menu, lines 2,3, & 4 in this are workflow actions (change status).

        I'm wondering if this is suitable for you.

        Also, there is no ACL applied to individual workflow transitions - i.e. you cannot have permission to reopen, but not close etc.

        Show
        Tony Stevenson added a comment - Chris, Please see this attachment - you will see the far right of the image is the context menu, lines 2,3, & 4 in this are workflow actions (change status). I'm wondering if this is suitable for you. Also, there is no ACL applied to individual workflow transitions - i.e. you cannot have permission to reopen, but not close etc.
        Hide
        Chris Lambert added a comment -
        {quote}
        This is not a good idea, as it means adding new column (with statuses) will mean modifying the workflow and leaving some tickets in an abandoned state
        {quote}

        Certainly there's risk but I think all I need are some ACLs changed on _existing_ transitions (e.g. In Progress -> Open for non-assignees) and then some extra fields added ("sprint"). I could be missing something here, but we (well, not me) have done this successfully on other JIRA instances.

        {quote}
        Can you not achieve the same result from the filter review page, and quickly changing the status. The upcoming upgrade to 5.2 makes this very simple indeed.
        {quote}

        I'm not sure what you mean by _filter review page_? I don't see any way for me to change the state for a ticket that is not assigned to me, which is what I think I need to be able to do.

        Thoughts?
        Show
        Chris Lambert added a comment - {quote} This is not a good idea, as it means adding new column (with statuses) will mean modifying the workflow and leaving some tickets in an abandoned state {quote} Certainly there's risk but I think all I need are some ACLs changed on _existing_ transitions (e.g. In Progress -> Open for non-assignees) and then some extra fields added ("sprint"). I could be missing something here, but we (well, not me) have done this successfully on other JIRA instances. {quote} Can you not achieve the same result from the filter review page, and quickly changing the status. The upcoming upgrade to 5.2 makes this very simple indeed. {quote} I'm not sure what you mean by _filter review page_? I don't see any way for me to change the state for a ticket that is not assigned to me, which is what I think I need to be able to do. Thoughts?
        Hide
        Tony Stevenson added a comment -
        Your project needs a custom workflow for this, and enabled so that greenhopper can manage the workflow. This is not a good idea, as it means adding new column (with statuses) will mean modifying the workflow and leaving some tickets in an abandoned state, which is quite hard to recover from.
        Can you not achieve the same result from the filter review page, and quickly changing the status. The upcoming upgrade to 5.2 makes this very simple indeed.
        Show
        Tony Stevenson added a comment - Your project needs a custom workflow for this, and enabled so that greenhopper can manage the workflow. This is not a good idea, as it means adding new column (with statuses) will mean modifying the workflow and leaving some tickets in an abandoned state, which is quite hard to recover from. Can you not achieve the same result from the filter review page, and quickly changing the status. The upcoming upgrade to 5.2 makes this very simple indeed.

          People

          • Assignee:
            Unassigned
            Reporter:
            Chris Lambert
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development