nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issue status text not shown

Jens Bode_dbqqc9

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'

Bildschirmfoto 2025-02-20 um 08.39.08.png

But for all other types it´s shown like this example.

Bildschirmfoto 2025-02-20 um 08.39.20.png

What´s wrong with this issue type??

Accepted answers

Tuncay Senturk _Snapbytes_

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.

Dick

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

Bill Sheboy

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

All comments

Tuncay Senturk _Snapbytes_

Hi @Jens Bode

Dick

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.

Kind regards,

Dick

Jens Bode_dbqqc9

This is our workflow. Did you mean transition or what kind of action to you talk about?
Bildschirmfoto 2025-02-20 um 09.40.28.png

Jens Bode_dbqqc9

All issue type use the same workflow and I checked this behavior in different browser (chrome and safari).

Dick

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

Jens Bode_dbqqc9

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

Bill Sheboy

Hi @Jens Bode -- Welcome to the Atlassian Community!

Kind regards,
Bill

Jens Bode_dbqqc9

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud