All of the issues of a certain issue type do not have transition buttons

Angela Tran July 12, 2016

We can only transition these with our Kanban board, so it is not a permissions issue. The other issue types have transition buttons. I tried integrity check, but i'm getting a time out error. I also copied the workflow and switched the issue type to the copy of the workflow. That didn't work either. 

1 answer

0 votes
Chris Solgat
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 12, 2016

First thing I would check is the workflow itself (especially if the issue type has it's own).  More specifically, I would check for any Transition Conditions that may reference an issue type, or some other field that may be unique to the issue type.  Even if these specifically don't work, you need to find out the other things that are unique to that issue type.

As for Integrity Check (don't know if it works the same on Cloud), you will likely need to use a "Proxy-Bypass" link.  You will need either your Server IP address or the Server's registered Name/ID.  You will also need the port number as well.  Your new URL would look something like https://127.0.0.0:8080/jira/secure/admin/IntegrityChecker!default.jspa

Angela Tran July 12, 2016

I checked the workflow and there aren't any unique conditions or validators. The workflow itself is pretty simple. I tried the Integrity Checker link and I got an ERR_SSL_PROTOCOL_ERROR. Also, I noticed that this problem started happening after we migrated our JIRA instance to a new server.

Chris Solgat
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 12, 2016

That's typically a certificate error.  Does your normal JIRA URL use "https://" or "http://".  If the normal URL uses "http://", then make sure you use the same on your proxy_bypass URL.

When you say you noticed this after JIRA was migrated, did you mean the problem related to the Issue Type?

You said you checked the workflow, but just for clarification, did you check the Create transition as well?
Have you checked the log files too?  Are there any errors that correlate with the Creation times of those issues?  

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events