We create a new team-managed Kanban project with it´s own workflow. This workflow is assigned to all issue types, but not status will be shown for the issue type 'task'
But for all other types it´s shown like this example.
What´s wrong with this issue type??
Hi @Jens Bode -- Welcome to the Atlassian Community!
FYI -- I recall several community posts with this same symptom in the last couple of weeks. I recommend searching for those to learn if there is an open defect or some common, project configuration problem that could be corrected.
Kind regards,
Bill
Looks like a known bug at Atlassian. Caused by deleting a status inside the workflow. I have to contact the support to let them fix it for us.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Tag @Jens Bode
In order to make a good working workflow, you need to discern between the status and the action that brings a ticket from a status to another status.
In your case the action has no name defined.
In the version of Jira I'm running, the name of the action is one of the property-value pairs associated with the action (the arrow in a workflow). I believe in the Cloud version, the interface has been modified, but the main message remains: discern between the status and the action, and define both.
Kind regards,
Dick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jens Bode
The lightning symbols represent actions (as per your top picture).
I'm not seeing these symbols in the lower part of your workflow (which doesn't seem to have the Implementierung action from your top picture, which confuses me). I take it the top two pictures are the new interface where the actions are defined?
Atlassian has documentation on useful properties, maybe that can help you out.
Mind you, that in general it's not recommended (or logical to a user) to name actions exactly the same as the statuses they end up in. It also makes configuration a lot harder.
Kind regards,
Dick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The transitions with the lightning symbol has rule for the automation like autoassigment to specific users. They have no properties you linked at your reply.
What it makes totally wired is that this only happens for TASKs and not for BUG, EPIC and STORY issue types.
I have created a new issue type to test if there is problem in the configuration but the behavior of the new issue type is the same :(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Your workflow Scheme can discern between issue types. Have you looked that up?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm under the impression that you can/should be able to make a complete workflow.
That includes making/adjusting a Workflow Scheme for you entire project (meaning that you get to configure the workflow for all issue types that are available in your project. You do so inside the workflow scheme that is linked to your project).
As you state that you can create new issue types, you also should be able tell Jira which workflow these issue types should follow. Again, that's done in the Workflow Scheme.
Kind regards
Dick
In hindsight (and absolutely not meant in a judgmental way), it might've been perhaps easier for you to ask your admin for a company managed project, as the journey you're now undertaking is one that is very familiar to your admin. Let him/her help you get on track, it's his/her job!
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.
To be honest, @Jens Bode I could see from your workflow that you were very focused on capturing the actual way that you wanted to work in your team, within the Jira workflow.
Don't be surprised if your admin will propose a workflow that:
Just a friendly heads-up,
Kind regards,
Dick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Another user gave me the hint, that this behavior is a known bug at Atlassian and we have to contact the support to fix it.
Root cause: Deleting a status from the workflow :/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jens Bode
That's strange. Have you checked the workflow for the Task issue type? Confirm that the workflow appears correct and the statuses are accurately mapped. While this isn't expected behaviour, it’s possible that the statuses may have been deleted or corrupted (take this with a pinch of salt please, I am just guessing as this is very odd). If everything seems fine, I'd suggest raising a ticket with Atlassian support.
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.