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

New issues created default to "Done"

Alex Caine

Whenever I create an issue in Service Management or Jira Kanban board the issue immediately gets marked as "Done." This behavior started randomly, and it's messing with my automation. The workflows looks normal and don't seem to indicate that an issue would move from Open to Done automatically as default. Any help please?

Accepted answers

Nic Brough -Adaptavist-

When you say "marked as done", do you mean it gets crossed out as "resolved", or do you mean "it gets created in the to-do status, but then transitions to a done status"?

If it's the first of those, then check your create screens and post-functions, make sure the resolution is not on screen and not being set by a post-function

If it's the second of these, then start by checking the history - who changed the status and when?

If it's something else, then please explain more!

Joseph Chung Yin

@Alex Caine

I agreed with @Nic Brough -Adaptavist- statement. In addition, Kanban/Scrum boards are associated with Jira Software projects and not for JSM projects. In JSM projects, all issues are tracked via Queues concept.

I would also recommend you to investigate your Automation rules to ensure there are no rules making the improper status transition or setting the resolution field incorrectly.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

All comments

Nic Brough -Adaptavist-

When you say "marked as done", do you mean it gets crossed out as "resolved", or do you mean "it gets created in the to-do status, but then transitions to a done status"?

If it's the first of those, then check your create screens and post-functions, make sure the resolution is not on screen and not being set by a post-function

If it's the second of these, then start by checking the history - who changed the status and when?

If it's something else, then please explain more!

Joseph Chung Yin

@Alex Caine

I would also recommend you to investigate your Automation rules to ensure there are no rules making the improper status transition or setting the resolution field incorrectly.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Alex Caine

For the Jira Boards, when I manually create a new issue and save it, it's marked with a "Done" status, and I have to go find it and change the status to either backlog, to-do etc. This didn't happen initially which is odd.

In JSM I'm experiencing similar behavior, but with the Automation so I assume it is in fact related to that. However, my automation is very simple and only involves creating a task each Monday, nothing related to statuses, and the fact that my new issues on Jira scrum board are doing the same makes me assume the behavior is related somehow.

Alex Caine

Screen Shot 2021-10-18 at 12.36.29 PM.png

Alex Caine

If I manually create a task it defaults to "open," but when this automation runs it defaults to "Done." This is a queue I created to keep a record of resolved work items since they would essentially just disappear otherwise.

Joseph Chung Yin

@Alex Caine -

Did you had a chance to look at the WF for Task issue type in the General Requests project to ensure there is no post-function incorrectly transitioning the issue?

Another question, when you manually create a task, are you creating the task in the same project?

Best, Joseph

Nic Brough -Adaptavist-

Ok, so what does the history say? Who moved it through the transition from "to do" to "done", and when?

Alex Caine

Screen Shot 2021-10-18 at 2.03.31 PM.png

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management