Hello, we started to see the new field "Sprint[Checkboxes]" that appeared along the default "Sprint - cf[10020]" which started to break our scripts, since in the past we were using JQL directly "Sprint= ". Now it fails with There are multiple custom fields with the name 'sprint'. Try using one of the following terms: cf[10020], "Sprint[Checkboxes]" How can we remove this dropdown field ? That is not visible in custom fields

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

The source of the new field "Sprint[Checkboxes]"

Maksim Beliaev

Hello,

we started to see the new field "Sprint[Checkboxes]" that appeared along the default "Sprint - cf[10020]" which started to break our scripts, since in the past we were using JQL directly "Sprint=<sprint name>". Now it fails with

There are multiple custom fields with the name 'sprint'. Try using one of the following terms: cf[10020], "Sprint[Checkboxes]"

How can we remove this dropdown field ? That is not visible in custom fields

Accepted answers

Marc -Devoteam-

Hi @Maksim Beliaev

Check on the availability of Team Managed projects and check f the field is in one of those projects.

All comments

Marc -Devoteam-

Hi @Maksim Beliaev

Check on the availability of Team Managed projects and check f the field is in one of those projects.

Maksim Beliaev

hi @Marc -Devoteam-

Team Managed are indeed available. But how can I find which project has it and more important how do I prevent such fields to be created or propagated to company managed ?

Marc -Devoteam-

Hi @Maksim Beliaev

You need to check every team managed project, as they are silos.

In JQL this can't be prevented as information on the field and its values are stored in the index, to be usable on searching.

you can't prevent them to be created, every admin on a team managed project is able to create fields to be used in that particular project.

they can also change the screens, workflow etc in a team managed project.

Prevention is to disallow usage of team managed projects in your instance, you can remove al rights to this option in global permissions settings of Jira.

Maksim Beliaev

you are right, we were able to nail it down

thank you!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud