Tickets will not open
When a ticket goes into a certain status the the ticket will no longer open. The status we have is called Peer Review. But once we disable the Workflow addon the ticket is able to be open
Comments (10)
-
repo owner -
reporter - I am not sure what version we had before. But we updated all addons and still had this issue
- The tickets just sit at the loading screen. Then Jira will state, the issue can't be displayed right now
- Peer Review
-
reporter Looks like it is related to the conditions on Peer Review. Once I removed those the ticket opens quickly. Were they added incorrectly?
-
repo owner Can you please run the following 2 JQL queries in your JIRA instance, and tell me how many issues return each of them?
1)
labels != UX OR labels is EMPTY
2)
labels = UX
-
reporter Here you go
1) 291933 for all tickets. I ran project = key and labels is EMPTY and that showed 8600
2) 256
-
repo owner Please, replace "Condition based on JQL query" with "Boolean condition with math, date-time or text-string terms" using the following boolean expressions:
1) Transition "Ready for UX Grooming (481) " and "Ready for UX (451)" which now are using 'labels = UX' JQL query:
%{00080} = "UX"
or if you want to only check if whether it contains label "UX" among other labels:
%{00080} ~ "UX"
2) Transition "Ready to be QA'ed (211)" which now is using 'labels != UX OR labels is EMPTY' JQL query:
%{00080} != "UX"
or if you want to only check if whether it doesn't contain label "UX" among other labels:
%{00080} !~ "UX"
Note that %{00080} is field code for Labels.
-
repo owner Hi Leland,
The solution I gave you in my previous post should solve your problem, but I have made a modification in version 2.2.23_beta_1. Can you please install this version and tell me whether it solves your problem?
-
reporter I just tested out the Beta version and that fixed it my test server.
-
repo owner Thanks for the testing. Now, I recommend you to apply in your production server the modifications I explained you in my former post, in case you don't want to install the beta version in your production server.
-
repo owner - changed status to resolved
Fixed in just released version 2.2.23.
- Log in to comment
Hi Lowe,
I need the following information in order to find out what is happening: