Is it normal for a workflow publish with only a single issue type addition require issues types not associated with the project to be mapped?

Peter Franzek1

Adding a new issue type to a Project. The Project uses a unique workflow that is NOT shared with other projects.

The issue type was created and associated with the Project. The issue type has been added to the workflow using the workflow editor. When the Publish button is used the Publish Workflow dialog appears requesting a large number of Jira Issue Types and their status to be mapped to the Project workflow status. The Jira Issue types are not in use with this Project and have never been used.

Is this normal behavior?

Other info:

Attached picture of workflow and publish workflow dialog.

The Issue Type was added prior to the last OnDemand update.

Nic Brough -Adaptavist-

Yes, it's listing them by default because they are there. I suspect you've also set your workflow scheme to use that workflow as the default for all issue types. It is just a flat "look at all the issue types in the system", because they *might* be in use.

Simple trick though - look at the numbers next to the issue types - where they are 0, you can ignore them because there are no affected issues.