Problem with Publish Draft Workflow dialog screen.

[Teja]

Hi Team,

We have issue with publishing workflow after hit the button will grayed out and refresh page will show "No workflow with name 'GT Bugs - Production Patch Bug Workflow v25'could be found." message.

Please see the attached screen shot

 

Thanks

[Andy Heinzer]

Not sure why you would see this exactly.  But if this hangs here, it sounds like something on the backend got stuck or failed to complete this action.  I would start by recreating this problem, and then immediately looking into the $JIRAHOME/log/atlassian-jira.log file to look for any stacktraces/errors that happen when trying to publish/overwrite this workflow.

If there is something timing out on the database end, or some other error the stacktrace there should give us a lot more information to work with in order to try to understand why this might be happening.

[Teja]

Hello @Andy Heinzer Thank you.

I found this error message in atlassian-jira.log file "ERROR tnaik 476x47192x1 1g518vj 10.230.60.101 /secure/admin/ViewFieldScreens.jspa [webwork.util.ValueStack] METHOD: "workflowTransitionViews", exception: 
java.lang.IllegalArgumentException: Cannot find Screen with id '13108'." 

Thanks

Tejas 

[Andy Heinzer]

@Teja Thanks for that error, it is very clear now that you are seeing the problem described in this KB: Workflow error: Cannot find Screen with id 'xxxxx'

In order to correct this problem, you will need to access the SQL database that Jira is using and run a few SQL statements to modify your data.  Before you do this I would recommend that you stop Jira, and create a backup of your database, as changes of this nature are not officially supported and if done incorrectly, you might need to revert the database data back to the backup to keep things working.

If you have any questions about following the steps in that KB, please let me know.

Andy

[Teja]

Hi @Andy Heinzer I executed this query SELECT * FROM jiraschema.jiraworkflows WHERE DESCRIPTOR LIKE '%13108%'; in our SQL database and found the workflow which is using null screen transition. And I went back to the application and deleted screen i.e null in the workflow transition and changed it to appropriate screen and restarted the Jira service but its still hangs up. Do we need to do the re-index? 

Thanks

[Andy Heinzer]

The KB didn't say to it that way.  It might not be appropriate to try to correct the problem that way.  I would suggest sticking very closely to the details of the KB itself.  It might be best to revert your changes in SQL first, and then try to follow this KB precisely.  

On a side note the KB does mention that if you follow it correctly a draft of that workflow could also have this problem:

If after following the steps you continue to get the error when trying to edit the workflow, check if you don't have a Draft already created. If yes, then discard it and create a new one.

So perhaps that is something you might be hitting up against if your steps were correct, but so far I'm not sure that was the appropriate way to fix this.

Let me know if you restored the database either way, and then I'd suggest starting over with the KB.  Please let me know the results of the SQL select statements.  Perhaps I can help you craft the SQL update statement for your system this way.

[Teja]

Hi @Andy Heinzer My apologies for replying late.
After doing all the above[DB restore & update from the DB], we are still facing the issue. I believe Workflow error: Cannot find Screen with id 'xxxxx' is not the root cause of this problem. We have same error message in our production Jira attallasian-jira.log file but Publish Draft Workflow dialog screen will not hang up.

[Andy Heinzer]

Hi Tejas,

I have created a support ticket for this issue over at https://getsupport.atlassian.com/servicedesk/customer/portal/20/GHS-144688

I have also requested that we gather logs from your system to better be able to troubleshoot this issue.

Thanks

Andy