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

Retiring old ticket types, but not migrating to new types

philipf

Hello,

I have 5 ticket types in a board, that are being replaced with 5 new ticket types.

The old ticket types can't be migrated to the new ticket types since we are rethinking how the tickets will work in a legal focused board.

So what would be the best way to not have the option to create any new old tickets, but let the existing ones remain and close themselves out.

We do not want to map to new ticket types. Just not let people create new ones.

I looked in issue security but the topic is just create a scheme, I then added a group, and left with nothing.

Accepted answers

Trudy Claspill

Hello @philipf

Is this for a Company Managed project or a Team Managed project?

In a Company Managed project there is no native method to limit which issue types can be used during issue creation, other than removing the issue types from the Issue Type Scheme used by the project. And if you remove them from the scheme, then the affected issues have to be assigned to an issue type that remains in the scheme.

There might be a method to do this with a third party app, if you are willing to consider that.

Issue Security is used to set the visibility of issues. The implementation of that feature is different between Company and Team managed projects.

In Company Managed project issue security is not associated directly to an issue type. Instead you define "security levels". A security level value is set for each issue. The security level specifies who can see that particular issue. It does not impact the creation of issue, but rather who can see them after they have been created.

All comments

Trudy Claspill

Hello @philipf

Is this for a Company Managed project or a Team Managed project?

There might be a method to do this with a third party app, if you are willing to consider that.

Issue Security is used to set the visibility of issues. The implementation of that feature is different between Company and Team managed projects.

philipf

it is a company project, and we just want people not to see them so the solution works above.

however:

1. I created a new security scheme

2. added a new group

then what, where do I tell it to only let this group show the tickets. None of us can figure out how we tell the system to perform the security permission rule.

philipf

but thinking of this further, does it mean that people who aren't in this group won't be able to see those tickets at all, we just don't want it to be in the drop-down when selecting ticket type to create.

Trudy Claspill

Issue Security has no impact on the issue type being available in the Create Issue function.

Issue Security is only about the visibility of issues that already exist.

There is no native method to limit which issue types can be used during issue creation, other than removing the issue types from the Issue Type Scheme used by the project. And if you remove them from the scheme, then the affected issues have to be assigned to an issue type that remains in the scheme.

There might be a method to do this with a third party app, if you are willing to consider that.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud