Hi community,
I have a very strange behavior in one of my Jira projects.
My workflow looks like this:
... - In Development - In Pull Request Review - In Test - ...
There are some Github Enterprise triggers between these steps, that when a pull request is created and a pull request is merged, the ticket will be set automatically to the next step.
The transition works, but it's not shown in the history which breaks our reports.
How is this possible and how can I fix this?
Best regards
I have a customer with a similar case, an automation rule transitions the issue, it shows in the correct state, but the history is missing the action.
Where you able to address your issue @Christopher Mayr
Unfortunately not solved yet, we already had several meetings with Atlassian and they can't reproduce it and so we didn't get a good solution.
Current guess is that an add on on our instance is the problem, we will try this in safe mode during our next update.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for getting back @Christopher Mayr
To bad this is still an open case. I'll continue my investigation, when I find something I'll be sure to leave a comment in case it can also help you out.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have the same type of set up that when a pull request is created and a pull request is merged, the issue will be set automatically to the next step in our workflow. Yesterday I saw that the change of status is not logged in history any more but have been done before.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.