JQL results include Issues that have changed Type

[Erin Liva]

I was creating a quick JQL filter to find all the Issues in the Sprint that wasn't with a status of Cancelled so I could export the list. The results however brought up 1 extra issue that is of type Subtask. Researching it produced a theory that when an issue type changes, it still retains the previous type somewhere and JQL includes it even though it is no longer that type. See image below.  If intentional, is there a way to say only the LATEST type to ensure these don't show up or is there a bug fix?

[Trudy Claspill]

Hello @Erin Liva 

Your query has not information about types. I don't think that the backend is looking at issue types at all. The subtask may be getting included because when it was a Story its Sprint field got set, and when it was converted to a Subtask that field was not automatically cleared.

You can exclude subtasks from your filter results by adding the following to the JQL:

and issuetype not in subTaskIssueTypes()

[Erin Liva]

Hi @Trudy Claspill I don't normally need to specify an issue type. All of the Subtasks under that Requirement/Story has the sprint field set to the same value so I don't think that would be the reason. I compared all the subtasks under the story and the only thing that stands out is that the 1 subtask used to be a story.

I can put in your JQL suggestion to get my extract but this seems like either a bug or non-documented behavior.

But thank you for looking into it!

[Trudy Claspill]

I did some experimentation based on your response. I thought that the Sprint was inferred from the parent rather than explicitly set on sub-tasks, but I was wrong. You're right, the sprint field is explicitly set.

I recommend that you ask your Jira Administrators, if you aren't one, to open a support case directly with Atlassian to ask about this. 

https://support.atlassian.com/contact/#

If it turns out to be a bug it would be great if you post back here the link to it.

[Erin Liva]

https://support.atlassian.com/requests/JST-1090464 is the support ticket number

[Trudy Claspill]

We won't be able to see the support ticket.

If they respond with a new bug or change request link, please post it here. Then we can upvote it.

[Erin Liva]

@Trudy Claspill below is the answer I got from support. It doesn't explain why a subtask (that used to be a Task then made a Story then made a Subtask) kept appearing on the JQL results (it was the only subtask of many that showed up in the results). I suspected it was because the issue changed types from the initial type which would normally show in my JQL results in a Team managed project and somehow retained a history of that conversion.  Here was the final response.:  

After doing some further research, I did find that for team-managed projects, it is currently expected that sub-tasks will not show up in the JQL results when filtering on a sprint.

I found two related tickets, one is a feature request and one is a bug ticket:

• FR: Ability to have Team Managed Project (TMP) Subtasks shown in the Company Managed Project (CMP) Active sprint board when directly creating from Parent issue.
  • This mentions similar to what you shared: team-managed subtasks will sometimes show if they are converted from standard issues to subtasks
• Bug: Unable to search for subtasks when filtered by sprint
  • This relates more to a bug itself, and explains that the expected result when filtering on sprint should be to see all issues including subtasks in the JQL results

We encourage you to add yourself as a watcher to be kept informed as to the state of the feature/bug moving forward.