nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

change jira status if commented!

Samuel

Hi,

is there any way that we can change the status if someone comment on the ticket?

Like if someone made a comment on any Ticket and the status automatically shows like "User Responded"? I tried to customize the workflow transition but i cant find a way to do this. Please help1

Accepted answers

Nic Brough -Adaptavist-

Yes, that's exactly what the auto-transition listener was written for. See https://ecosystem.atlassian.net/wiki/display/JTOOL/Auto+Transition+Listener

All comments

Nic Brough -Adaptavist-

Yes, that's exactly what the auto-transition listener was written for. See https://ecosystem.atlassian.net/wiki/display/JTOOL/Auto+Transition+Listener

Samuel

Its not working for me or may be i havent setup correctly. want - "if someone comment on any ticket, the status just shows to reporter "user responded" and if assignee reply to that comment" it should show to reporter or commenter as "Awaiting Response".... regardless of the workflow status.

Is this possible in JIRA?

Nic Brough -Adaptavist-

It's working for me on several Jira instances, so yes, it's perfectly possible and you probably have not set it up correctly.

However, "it should show to reporter or commenter as "Awaiting Response".... regardless of the workflow status." is nonesense. If "Awaiting response" is a status, then you need to move into that status. You need to decide if that really is a status, or just a flag that is on the issue and not part of the workflow. If it's a non-status flag, then the auto-transition listener is of no use to you, and you need to find/write a listener that will set it separately and then work out something else that will remove it when necessary.

Jan Cornelissen

Nic, any chance you can tell us when JTOOL-203 will be adressed? It's a bug reported almost a year ago. and I can't seem te comment on the issue.

Samuel

Oh yes, it worked!! Thanks Nic, appreciate your help.

Nic Brough -Adaptavist-

Not a clue, I'm not an Atlassian, so I don't have any more information on development issues than you do. You should be able to comment/vote on that issue if you have an Atlassian id though.

Jan Cornelissen

, ok I'm sorry!!

Nic Brough -Adaptavist-

No problem ;-) It's worth voting and adding a comment if you can though. Atlassian do consider votes when deciding what to tackle next (it's not the only thing they look at, but it is used)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration