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

Remove "Development" field from task details

Brendan Horsfield

Hi there,

I have recently created a new project in Jira Software (Cloud) to help my team keep track of their weekly tasks. None of our work is software-related -- we are just using Jira like a simple Kanban board.

Unfortunately, every new epic & task I create contains a "Development" field that allows the assignees to create new branches and commits in my Bitbucket repository! The Bitbucket repo is completely unrelated to the Jira project, and my team should definitely not have access to it in any way.

Can anyone tell me how to remove the "Development" field from the epic & task descriptions in Jira?

Note that I am using the free version of Jira Software at the moment, so all users are automatically granted Administrator status.

Thanks & Regards,

Brendan.

Accepted answers

Brendan Horsfield

Solution:

Upgraded Jira subscription from Free to Standard plan.
Opened Jira project, went to Project settings > Access
Selected Manage Roles
Created a new role that contained only the necessary permissions required by team members
Assigned the new role to each team member, and deselected any previous roles

Final comment: The above procedure must unfortunately be performed for every new Jira project. A better solution might be to use the Field Configurations feature in Jira Software. This allows the project administrator to set up a custom issue format that will be used for all new issues in a project, regardless of user permission level. However, I will leave this as a challenge for another day!

All comments

Dave Mathijs

Hi @Brendan Horsfield , are you using a company-managed or a team-managed project?

In a company-managed project, you can remove everyone from the View Development Tools permission in the permission scheme associated with the project. Please note that the permission scheme may be shared with other projects who need to see the development tools.

In a team-managed project, you simply toggle off the Development > Code feature in Project Settings > Features.

Brendan Horsfield

Hi Dave,

I am in a team-managed project. I have already tried toggling off the Development > Code feature a couple of times, but it made no difference.

Do I need to shut down & reopen my browser in order for this change to take effect?

Brendan.

Brendan Horsfield

Hi Dave,

I have been digging through the settings for my Jira project, and it is starting to look like the Development panel is a locked feature. The menu path I have followed is:

Settings > Jira Settings > Issues
Fields > Field configurations in the left-hand panel
Wait for View Field Configurations screen to load, and then select Default Field Configuration
Scroll down to Development. You will see that this field is labelled LOCKED and cannot be changed

Really hoping there is a fix for this. One of my team members is from another company, and if I can't prevent them from accessing our Bitbucket repository via this Jira project, then we simply cannot use Jira at all.

Regards,

Brendan.

Brendan Horsfield

Starting to think this might be a permissions issue. We are currently on the Free plan, where every user is classed as an Administrator. We might need to switch to the Standard plan in order to resolve this problem.

Brendan Horsfield

Solution:

Upgraded Jira subscription from Free to Standard plan.
Opened Jira project, went to Project settings > Access
Selected Manage Roles
Created a new role that contained only the necessary permissions required by team members
Assigned the new role to each team member, and deselected any previous roles

Vinod Kotiya

This work. Really what pitty. Even not mentioned in documentation. Business users complain for these fields and no easy way to remove it. Seriously Atlassian.

Micheal Planck

When you're editing a field configuration, you can add, delete, or hide fields.

Why can't you do that with this one?

Everything Atlassian does is so minimal. There's never any sense of completeness; any method or approach that just works for everything.

Jira Work Management doesn't have these fields; but Jira Work Management is un-usuable, because its Timeline cannot fold Tasks into their Epics, because JWM doesn't think you should be using Epics in the first place. Instead, JWM folds sub-tasks under their tasks on the timeline, while Jira Software cannot show sub-tasks at all on the timeline.

Tobias H

Just leaving this here in case someone stumbles upon this in hopes to hide Development Tools in a Team Managed project

Go to Project Settings > Features and disable:
1. Code
2. Security
3. Releases
Under Project Settings > Access
1. Change Project access into Limited
  1. Bear in mind that you will need to invite everyone who should have access now, as default "Open" permissions will no longer apply.
2. Press Manage Roles and create new roles by copying the default ones, but make sure to uncheck "Access to Development Tools"
Now, finally, your users won't be able to see the Development section on Issue view.

Why does it need to be so hard? I have no idea.

David Washburn

This doesn't seem to work anymore. I created a new administrator role and removed the access to dev tools but it's still present, sadly.

Christian Zendo - Computerra

Hi there,

we remove the main "Development" part in the issue detail view by browsing Project Settings -> Issues -> Layout -> Edit Issue Layout -> REMOVE the "Development" Field.

Karen_v1eify

this does work, just make sure that the people have ONLY that new role assigned to them

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-software

jira-software-cloud