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; } } }

Changing issue status in "Edit Jira Issue Screen"

Pierre Kuhl

As far I see I am not able to change the status of an issue in the Edit-Issue screen.

That makes integrations like the realtimeboard one a bit useless (beside a strange usability in general) because I can't change the state in realtimeboard but instead I have to switch for and back to jira

- Am I wrong does anybody know how to achieve that?

- or is a work around available?

Accepted answers

Pierre Kuhl

Hi Alexey,

I am working with Jira Cloud

- no you can't change the status in the edit jira issue screen.

Keep in mind I am talking about exactly this screen (see attached screenshot) the columns you are probably referring to are not part of that "overlay"-Screen.

All comments

Alexey Matveev

Hello,

You change a status in Jira in the issue view screen. There are buttons on the panel with the names of your transitions.

Statuses are connected between each other by transitions. You push the button for a transition to move to the required status.

In Jira Cloud in the new Issue UI, you change statuses. But I guess, you work in Jira Server.

Pierre Kuhl

Hi Alexey,

I am working with Jira Cloud

- no you can't change the status in the edit jira issue screen.

Keep in mind I am talking about exactly this screen (see attached screenshot) the columns you are probably referring to are not part of that "overlay"-Screen.

Nic Brough -Adaptavist-

Yes, that's correct. Status is not a field, it's an indication of where the issue is in the process. You can't "edit" it, because it's not a field, you need to move the issue through transitions to update it.

Pierre Kuhl

Hi Nic,

we are talking here about an user experience issue. No matter if it is a field or not, the term "editing" is not limited to input elements like a field. You can edit the issue type by using the drop down, too for e.g, . So you can even change the type of the issue, assignee, linked issues an so on but NOT the status. So why having all the possibilities in a third party tool integration but not being able to change the status? That forces you to switch from your Application like realtimeboard to another Jira Browser tab. That simply kills the flow especially doing remote team session when you share your screen. It is quite bad for being focused, means keeping your attention on the shown concept instead of a "screen flickering tab changing" is quite important.

Try to do kognitive walkthrough regarding the user Journey and you will probably get my point.

Nic Brough -Adaptavist-

<sigh>

I was answering your question about how it works, not talking about user experiences.

For what it's worth though, systems that have status as a simple editable field tend to have really poor data quality about the status because users don't have to think about it and just set what they want and forget it.

Pierre Kuhl

Strange argument because as you know the "change state functionality" is shown in the right column within Jira of the new Jira Cloud Design.
so you go for:
a) Jira will have poor data quality in the future
b) The Atlassian Team had the same opinion like me and changed it in their new Version but should have a look into their 3rd Party integration overlay to provide that there, too and improve UX

Your choice ;-)

I've asked for
I) Am I right with my assumption that I can't change it (approved before already)
II) possible workarounds (no answers yet)

Nic Brough -Adaptavist-

Why is it a strange argument? The drop-down, in my experience, leads to poor data quality. That's a poor choice made by Atlassian, not me, and I have already seen it lead to problems, with two clients suddenly asking how they can fix the 20% of their issues that are in the wrong status (previously around 1%). But given that the new UI on Cloud is a disaster, it's just one more failure in a massive pile of them. Also, it's not an "edit", the status selection triggers a transition.

Your assumption is correct, you can not (and never will be able to) "edit" a status. You have to use a transition to change it.

There are no "workarounds" - you have to use a transition to change status.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-cloud

jira-administration

user-experience

usability