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

Change ticket type of more than 1000 issues

UMONS

Hello,

I have a project "A", my goal is to transfer 1500 issues to another "Ticket Type" in the same project.

During this manipulation, the system tells me that it is not possible to make more than 1000 issues at the same time. Do you have a solution to do this without notifying the users/agents/stakeholders of the change?

Capture d’écran 2023-02-16 163403.png Thank you in advance for your answers

Accepted answers

Kai Becker

Hi @UMONS ,

this is limited to 1000 issues because of the performance.
Is there any problem in doing it in two bulk changes?

The only other solution I'm aware of would be api calls, but I think this does not make any sense in your situation.

All comments

Kai Becker

Hi @UMONS ,

this is limited to 1000 issues because of the performance.
Is there any problem in doing it in two bulk changes?

The only other solution I'm aware of would be api calls, but I think this does not make any sense in your situation.

UMONS

Hi @Kai Becker ,

No problem but how can i do two bulk ?

Best regards,

Kai Becker

Hi @UMONS ,

I guess you have a filter with the status of the corresponding issues. After changing the first 1000 issues, there should be 500 left, when you execute the filter once more.

If so, just make another bulk change with the left over issues and you should be good to go.

UMONS

hi @Kai Becker

If I perform the manipulation that I think you are proposing, it will notify all the agents and all the users attached to these exits, which is absolutely not desired

How to make it totally transparent ?

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management