closed task in new sprint

[Ivan Andrieiev]

why does a task that was closed, show as not closed when a sprint is closed and carried over to the next sprint?

[John Funk · Accepted solution]

Hi @Ivan Andrieiev 

Is the Task in the far right column of the board? Regardless of the status of the issue, it must be in the far right (last) column of the board to be considered Closed/Done/Finished/Completed.

[Ivan Andrieiev]

@John Funk  Hi 

yes, it is there

[John Funk]

Which issue was not carried over? And is there anything else that is unique about that issue from the other two that did get carried over? Are there any Sub-tasks? 

[Ivan Andrieiev]

there are no subtasks in more than one task, all tasks in the column have been moved. The common thing is that they were created through third-party services (not through Jira).

[Nic Brough -Adaptavist-]

You can't have sub-tasks that have more than one parent.

The question here is: "Does the issue that moved to the next sprint have any sub-tasks?"

If it does, then, those sub-tasks must be in the last column on the board, and visible in it.  Otherwise, the parent issue cannot be done.

[Ivan Andrieiev]

@Nic Brough -Adaptavist-  @John Funk 

there are no subtasks in these tasks. I know about the conditions you wrote.

[John Funk]

Is there anything unique about that one Story from the other Stories? Values for any fields that are drastically different besides maybe Story Points?

[Ivan Andrieiev]

what is unique about these tasks is that they were created through the Jira API using the messenger.

[John Funk]

And all of those get transferred to the next Sprint? 

[Ivan Andrieiev]

Yes

[Nic Brough -Adaptavist-]

The method of creation is irrelevant for this, unless you've somehow coded something for those issues to not be in the last column on the board somehow.

I think the next test is to directly compare every field on an issue that did move against one that did not (including the status of all the subtasks on an issue, and whether they are on the board or not)

[Ivan Andrieiev]

I didn't understand, can you be more detailed?

[Ivan Andrieiev]

@Nic Brough -Adaptavist-  @John Funk 

can someone help solve this problem or is it better to write to the support service?

[John Funk]

I would go ahead and contact support. 

[Nic Brough -Adaptavist-]

Have you looked at comparing an issue that did move against one that did not?

What, exactly, are the differences between their data (fields, sub-tasks, etc) other than the issue key, and how is your board configured?  (Status to column mappings, and what the board filter is)

[Ivan Andrieiev]

the board is configured, like all boards, we have a board where the tasks also create a bot through the API, but there is no such problem

[Ivan Andrieiev]

@Nic Brough -Adaptavist-  @John Funk My fault was in doing the wrong job. I solved the problem. Thank you for help.