we met a weird problem: there are a dozen of issues created which are in Open status. The problem is that we cannot set to In progress status - however the transition exists and there are NO conditions or properties on the transitions. All the users who tried it, have the particular permissions to do.
I tested the workflow on a different project and it worked: we could set the In progress status and saw the View workflow.
- The transition has no properties
- the transition has no condition
- The users have the particular View workflow rights and rights to set the In progress status
- The 'Start progress' button and the 'View workflow' link is hidden!
What can be wrong????
Thanks in advance!
>however the transition exists and there are NO validations, properties on the transitions.
"Conditions" are the things to look for on transitions. Validators check data as you go through the transition and properties beloing to them. Conditions are the thing that hide the transition when someone does not match.
>cannot see the View workflow link
Check that the permission scheme for the project has "view workflow" set for your users
Ok, time to look elsewhere - does this workflow work for other issues? I mean in the same project.
What do you get if you run the integrity checker? Transitions vanish if the issue has a damaged status/workflow and the integrity checker can find and fix it.
It's a long dull story, which I won't bore you with. The end result though, is that the current status of an issue is held in TWO sub-systems, and it needs to be the same in both. If it doesn't match, Jira gets confused and can't handle it, and throws lovely mysterious errors in odd places, while simply denying the users any transitional actions, and yet not actually telling them why.
The integrity checker will find and fix these...
Failed workflow migration, a system crash right in the middle of someone committing a transition, someone still trying things just as you're about to upgrade, or possibly network glitches. More recent versions of Jira are far more resistent to those errors, but they can still happen. I looked after a Jira that developed maybe one of these a week on Jira 3.0.3. Upgraded to 3.6 got that down to less than one a month, and 3.10 got it down to 1 every 3-6 months.
However, by a long way, the main culprit is people trying to be "clever". Changing things in the database is the main source of me getting contracts to undo the damage caused by "clever" people. Not far behind them are people who think it's clever to change the end-point of a transition while it's still running (custom plugins providing post-functions that mess things up)
On the bright side, it's usually easy to eliminate the "clever" things - if you trust your admins not to install badly-written plugins and your database people to not hack the database, it's all good.
But there's always a handful of these I never tracked down. It's vast amounts of effort to find something that might not even be reliably reproducible, so, as a proper Engineer, I gave up - it wasn't worth the time!
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs