Remove field from subtask
Asked by Alain Kovacs:

I have spent the last two hours googling and trying out stuff, and I feel like this should have a very simple solution, but I have not been able to find an answer to it..

I have the following subtask. I want to remove the Development field. This field has zero, nada, absolutely nothing to do with this project and for the life in me I can't figure it out. This is a service project in JSM, it has nothing to do with software..

![1.png](/t5/image/serverpage/image-id/337550i83E4884134A9FF8C/image-size/large?v=v2&px=999 "1.png")

For issues with a request type this is super easy, but since this is a sub task, I can not assign it a request type.. this is so incredibly dumb!

![6.png](/t5/image/serverpage/image-id/337565i574C691BF1B6BD0D/image-size/large?v=v2&px=999 "6.png")

Ok. So I have tried adjusting the field configuration scheme for this project. I have made a new field configuration for this issue type.

![2.png](/t5/image/serverpage/image-id/337554i68B7356D82A835ED/image-size/large?v=v2&px=999 "2.png")

This somewhat works. I can "Hide" certain fields, but not all. This being one of them. Why Jira? Why?

![3.png](/t5/image/serverpage/image-id/337555iBCA04C6B0E126DA5/image-size/large?v=v2&px=999 "3.png")

One other thing I have tried and is not working is using Scriptrunner's Behaviours. I don't want anybody to see that field (and a few others but it's a good start). I have made a fake group that does not have anybody in it. I have created a behaviour (in the screenshot below I was testing the standard example script, with priority, unsuccessfully...

![4.png](/t5/image/serverpage/image-id/337564i3A1E8FAE23D4AEEF/image-size/large?v=v2&px=999 "4.png")

![5.png](/t5/image/serverpage/image-id/337563iD49477659511B3B9/image-size/large?v=v2&px=999 "5.png")

If anybody can guide me in the right direction I will be really grateful! Thanks!


Answers:
author: Hans Polder
body: [@Alain Kovacs](/t5/user/viewprofilepage/user-id/5288524) ,

I agree this is somewhat confusing. I see the same behavior in my own test environment

As a workaround, I would attempt the following:

1) Go to Project Settings

2) At the bottom, go to 'Development tools'. Observe what is configured there.

3) Click 'Edit permissions'. Observe if the Permission Scheme is only being used by this project, or by multiple projects. If it's being applied to all Service projects, you could still proceed.

4) Go to 'View Development Tools' in the Permission Scheme and remove any roles listed there.

The Development Tools section will now be gone.

I would report this as feedback using any of the 'Give feedback' buttons they leave behind, as this feels like something they missed, and should be disabled in a less invasive manner than having to change the Permission Scheme for this.

comments: author: Alain Kovacs
body: Hi [@Hans Polder](/t5/user/viewprofilepage/user-id/5506451)

Thanks a lot for the quick answer! That did indeed remove that field.

Do you have an idea how I could remove the Request Type and Knowledge base also?

![7.png](https://community.atlassian.com/t5/image/serverpage/image-id/337583i5F4738B983C34E51/image-size/large?v=v2&px=999 "7.png")

The request type makes no sense, as a subtask can not have it, and we don't need the KB either.

Request type is locked also..

![8+.png](https://community.atlassian.com/t5/image/serverpage/image-id/337584i7859A960601B6A62/image-size/large?v=v2&px=999 "8+.png")


author: Hans Polder
body: [@Alain Kovacs](/t5/user/viewprofilepage/user-id/5288524) ,

Happy I could help!

I'm afraid not. This is more project-wide engrained and I can imagine you actually do want to keep using Request Types and KBs for the actual Service Mgt tickets :)

I would really suggest using the 'Give feedback' option in your JSM project, as I feel like this should be an improvement from Atlassian side.


author: Alain Kovacs
body: I thought so but thanks for confirming!


Tags: cloud

jira

jira-cloud

jira-service-management

jira-service-management-cloud