How do I transition a ticket to very bottom of next status?

[Cory Schulz]

Hi,

I am trying to figure out how to change the properties so that when I'm transitioning a ticket from one status to another that it goes directly to the bottom of the upcoming status column so I know what tickets have been moved to the succeeding column chronologically.

As of now it is so that if there are 8 tickets in the Work in Progress column and I want to transition the 4th ticket and the 2nd ticket (from the top) to the next status, Research Complete, and I move the 4th ticket first and then the 2nd ticket from top, the order of these tickets does not reflect when the ticket was moved there chronologically. It would still put the 2nd ticket above the 4th because of its position pertaining to the previous status.

Is there a way to change this? I want to know what tickets were completed based on when they transitioned to the Research Complete status and not based on their order from the previous status.

As you can see from the screen shots. the ticket moves in coherence with it's position from the previous status. It does not go directly to the bottom. As we have over 100 people working on this project, it would be confusing for them to have to move their ticket to the bottom of the initial status in order for it to transition to the very bottom of the next status.

I hope I haven't confused anyone. It's already doing my head in just trying to describe the issue.

Thanks very much,

Cory

[Nic Brough -Adaptavist- · Accepted solution]

No. You're either an admin, or you're not. There's no way to delegate this.

It is being looked at though - see https://jira.atlassian.com/browse/JRA-3156

For now, you'll need to be creative as Fabio says - make extensive use of roles in schemes, because your project admins can control who goes into which role (ideally, don't use groups at all in permission schemes)

[Daniel Wester]

We just listed Delegated Administrator for JIRA https://marketplace.atlassian.com/plugins/com.wittified.jira.delegated-admin which allows you to delegate the administration of project schemes to the project lead while still maintaining control as an administrator.

[Nic Brough -Adaptavist-]

<sound of bookmarks being added>

[Fabio Racobaldo _Catworkx_]

Hi Brad,

in my opinion the best way to do that is to manage the project permission scheme using the project roles. Each project administration can manage users/groups in specific project role.

Hope this helps.

Fabio