Duplicate issue types

Houston, we have a problem. Project-scoped issue types get unscoped when their projects are deleted (moved to trash).

I created a new NextGen project, at which time a new ‘Task’ issue type was created, scoped to the new project. In the result of a REST call to GET all issue types, I could see that the new ‘Task’ issue type was scoped to the new NextGen project.

  {
    "self": "https://projectbalmtest.atlassian.net/rest/api/2/issuetype/10413",
    "id": "10413",
    "description": "A small, distinct piece of work.",
    "iconUrl": "https://projectbalmtest.atlassian.net/secure/viewavatar?size=medium&avatarId=10318&avatarType=issuetype",
    "name": "Task",
    "untranslatedName": "Task",
    "subtask": false,
    "avatarId": 10318,
    "scope": {
      "type": "PROJECT",
      "project": {
        "id": "10455"
      }
    }
  }

Then I deleted (moved to trash) the NextGen project that I’d just created.

Now the list of issue types returned from the REST API still has the issue type that was previously scoped to the NextGen project, but its scope is unspecified; that is, it is indistinguishable from the other ‘Task’ issue types in the result.

  {
    "self": "https://projectbalmtest.atlassian.net/rest/api/2/issuetype/10413",
    "id": "10413",
    "description": "A small, distinct piece of work.",
    "iconUrl": "https://projectbalmtest.atlassian.net/secure/viewavatar?size=medium&avatarId=10318&avatarType=issuetype",
    "name": "Task",
    "untranslatedName": "Task",
    "subtask": false,
    "avatarId": 10318
  }
2 Likes

Hi @david.pinn,

Thanks for reporting this. I’ve created https://jira.atlassian.com/browse/JRACLOUD-75701 for the Jira team to address.

Regards,
Dugald

Hi @david.pinn, thanks for the report.

This bug is known, and is currently being tracked here. If you have anything you can add to the discourse, suggestions on what the behavior should be, or a story illustrating the problems this issue is causing you, please leave it there. You can also add a vote. Votes are a large part of how we prioritize bugfixes.

The Project Trash has been causing a bunch of problems recently, so we’ve had a lot of fires to put out. Fortunately, all of the other high-priority bugs have been squashed. This one is up next. Fingers crossed, it should be fixed in a couple weeks.