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

Cannot edit fields by bulk

Margo_ky7zv9

Hi All,

I try to edit some issues by bulk. Issues are from one project and issue type (so the same workflow) in different statuses. Bulk for status X works fine, but for Y, Z etc doesn't. 'Edit' option is available to me, but after all I can edit only some basic fields and most of them are under 'Unavailable actions'.

I cannot find any workflow property which causes this behaviour. Any idea what else can block editing certain system/custom fields by bulk?

Accepted answers

All comments

Rilwan Ahmed

Hi @Margo ,

Can you please share the JQL used for Bulk Edit ? From the screenshot, I see you have different projects and different issue types selected.

Margo_ky7zv9

Hi @Rilwan Ahmed - even if I put filter like project = XYZ and that's it, I can see the same errors:

NOTE: You do not have the required permissions in ALL projects of the selected issues to edit this field.

NOTE: You do not have the required permissions to edit this field.

Rilwan Ahmed

@Margo

Please check if your query is also getting Closed/Resolved/Done status tickets where you cannot edit ticket. When the ticket is closed, the workflow will not allow to Edit (if property is set). And similar property can be added to any status which blocks the edit.

I would suggest you to divide the JQL Like below so that you can easily identify which ticket is blocking the edits.
project = XYZ and Type = Task and Status !=Closed
project = XYZ and Type = Incident and Status !=Closed etc.

Margo_ky7zv9

I check with both statuscategory !=Done and statuscategory = Done

It's the same.

Some not Done statuses from the same workflow have editable fields, some not.

Properties on statuses are like:

jira.permission.edit.group.1 - and I'm in all groups

there is also something like

jira.permission.edit.userCF.1 - I'm not in this fields, but as far as I understand I need only one 'edit' property to be able to edit the issue.

Besides that, edit property allows me to be able to click on 'edit' issues at 'choose operation' screen. And here the issue is different, I cannot only edit some fields.

choose operation.PNG

I cannot see any restriction in field configurations or so.

davesoft11

@Margo and team,

I have a couple jira which have a label I want to change and I get the same:

"NOTE: You do not have the required permissions in ALL projects of the selected issues to edit this field"

error when I try to do it bulk. When I try to edit those jira individually, none of the permission-blocked fields are even presented.

Because you mentioned:

"jira.permission.edit.group"

I inspected the workflow to which these jira belong, and none of the transitions have any "properties" assigned at all.

Also, even when I am logged in as the Jira Administrator, I don't have the option to edit the labels on these (closed) jira.

Where else should I be looking to figure out how to change the labels on these jira?

Thanks!

Margo_ky7zv9

Hi @davesoft11

Have you checked permission schemes within these projects? You can be a Jira admin yet have no edit permission in a specific project/permission scheme.

KR,

Margo

davesoft11

@Margo

@Margo I checked the permission scheme and it says all logged in users have edit permissions.

I then checked the permissions helper and it says my user "has the 'Edit Issues' permission"

It may help to note that even if I go individually to this jira, I cannot edit anything. Inspecting the workflow and the transition to CLOSED, I see 4 properties, including:

jira.permission.edit.user: denied

So I think whomever created this workflow designed it this way (it predated me).

So how do I modify the permissions on an individual jira?

davesoft11

@Margo here's how I worked around not knowing how to change perms on an individual jira.

1. note that the workflow has the property to deny the permission when transitioning to CLOSED

2. note also that the workflow has a REOPEN transition which undoes that permission

3. REOPEN the jira, make necessary edits, then transition back to CLOSED

4. for jira that have a workflow that does not support REOPEN, use the "Move" feature to change their Issue Type to that used in (2). Then proceed with step 3. Then "Move" the jira back to its original Issue Type.

Pain in the butt, but it worked for the two jira I needed.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server

bulk