I edited the custom fields to remove a lot of information when doing a sub-task along with the "Component" and "Affects Version". When I come to post a sub-task, the fields of "Component" and "Affects Version" come back as mandatory fields.
What's going on here? I want them disabled and I see no reason to have to respecify a "Component" and "Affects Version" on a sub-task. Hopefully this is a configuration bug and not a usability issue.
How did you remove them?
Now the theory:
A field have several configurations that may affect whenther it shows up or not.
Depending on the configuration you have all three may be applicable to all issue types or you have a specific Screens, Field Context for each issue type.
How to find out:
You have to trace which field configuration is used for the particular Issue Type (sub-task) thatyou are trying to create. The steps below are for JIRA 6.1.
This will remove the field from all screens.
If you want to remove it from specific screen only let me know i will give you the steps for this as well.
I just realized that when I edited the "Sub-Task" fields, it edited them for "Create Issue" button as well. How do I only edit the issues for "Sub-Tasks"?
Is it this? https://confluence.atlassian.com/display/JIRA/Configuring+Sub-tasks#ConfiguringSub-tasks-Configuringsub-taskfieldsdisplayedonparentissues
edit: Ok so it's not that. Still trying to figure out how to only have certain fields when posting a sub-task vs a issue.
What do you mean by "sub-tasks window"?
You can customise the issue view, create and edit screens with screen-schemes, as already described above. Separate screen schemes, dependent on the issue type - works the same for top level and child issue types
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot