issue status change in Backlog view won't reflect in kanban

[Limor Hader]

Hi all -

I'm in the Backlog view with a bunch of issues in the backlog section and one in the Sprint section on top. 

I'm clicking an issue in the backlog section and from the issue details on the right pane, I change its status to "In Progress".

Unfortunately, nothing happens. The ticket remain where it is. It does not move to the sprint above, or appear in the In Progress column in the Kanban board. 

Seems like a UX glitch, unless I'm missing anything. 

1 or 2 things would help:

1) disable the status field dropdown while the ticket is in the Backlog section (doesn't seem to be possible)

or

2) once any status but Backlog is selected in dropdown, issue moves automatically to the Sprint section and to the appropriate column in the Kanban. 

Any ideas?

TIA for any help.

[Limor Hader]

@Kat Warner I agree. It can be tricky.... Thanks for your time in trying to figure this out. Here's a screen shot of the flow that would helpfully make it a bit clearer:

1. changed status from the right pane

2. status changed, and even after page refresh issue remains in Backlog (scrum)

3. in kanban, issue doesn't appear (of course because it has not moved to the sprint)

So now, the issue appears in Progress while it's not even in a spring. Doesn't seem like it is possible to disable this dropdown while issue is in backlog.

[Kat Warner]

At a quick glance it looks like you have a status called Backlog. This is likely associated with a kanban board column also called Backlog.

On the scrum board, a ticket will show in the 'backlog' section below the named sprints whenever the "sprint" field is not set to an open or future sprint regardless of the status.

[Limor Hader]

Thanks Kat. I'm aware of the 2 different fields, I just feel that since the status dropdown is so prominent, it could be confusing if it is set to In Progress although the ticket is not within a sprint. Ideally the status dropdown would be disabled until ticket is places in a sprint. 

Anyhow, moving along.. :)

Thanks much Kat and have a great day!

[Kat Warner]

Is this a classic or a next-gen project?

• with classic kanban projects, the backlog is a specific issue status,
• with classic scrum projects, the backlog is issues without a current or future sprint, and
• with next-gen kandban projects there is no field attribute that indicated if an issue is int he backlog or not. Issues are moved in and out of the backlog using drag-and-drop on the kanban backlog board view.

[Limor Hader]

Thanks for your answer, Kat. 

It's a classic scrum. I am aware about what the backlog represents here. The problem is that if I select "In Progress" from the dropdown in the right panel, the issue appears as if it's in progress while it is still in backlog. Confusing UX. 

[Kat Warner]

If changing the status of an issue moves the issue form backlog into a sprint there may be an automation or workflow post function operating here.

When you open NI-12 and look at History tab (normally this is set to Comment view by default) you should be able to see when the sprint field was change and by who.

[Kat Warner]

Unless you are referring to the Epic Status - which I find easy to confuse myself with the status of the Epic issue.

[Limor Hader]

Hi Kat, 

If changing of the status would move the issue into a sprint that would be good, but I don't believe this is possible. The only way it could move into a sprint is if I drag-drop it. Am I wrong?

Problem is that I change the issue's status to "in-progress" through the dropdown on the right panel, but issue remains in Backlog and never in a sprint, thus never appears in the kanban board. How can it be in progress if it's not in a sprint?...

[Kat Warner]

If the issue has the issue type "epic" then the ticket has two status fields. The 'epic 'status which can be changed in the right-hand side panel and the standard 'status' field which moves the issue through the workflow.

Where I work, epics are used to group issues together so are never put into sprints, only the issues associated with the epic are put into sprints. The 'epic status' field is updated automatically (using post-functions) when the epic issue status is changed. 

[Limor Hader]

The issue is a task, not an epic. Its status can be changed from the right-hand side panel. When changed to in-Progress using that dropdown menu below the issue's name (as appears in my image above), nothing else happens.

[Kat Warner]

Troubleshooting from a distance can be tricky.

What happens when you refresh the page? Some updates made in the right-hand panel view are not reflected correctly in the board list view immediately.