Hello,
For sub-tasks in our projects we do not want to show all of the fields that appear in the other issue types.
I thought I could do this by changing the Field Configuration that the sub-task reference in the Project Settings - Issue Types screen. However, I cannot find any way to change the Field Configuration that a sub-task references.
Thanks in advance for your thoughts!
Hi Katie,
Unless I am missing something, why can't you create a new Field Configuration and then associate the new Sub-task issue type to the new Field Configuration in the Field Configuration Scheme?
Hi John, thanks for answering. We may be missing an obvious step, but we couldn't find where to change the association between issue types and field configurations. I can see where the association is, but not where to change it. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John,
I modified the custom field configuration scheme so that sub-tasks aren't included in the applicable issue type list. When I created a new sub-task in our project afterwards, it was essentially a blank subtask with none of the fields configured appearing in the task.
Am I taking the right approach here? Am I missing a step?
Thanks!
Grace
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Grace - you are mixing apples and oranges. You are showing screenshots of connecting a custom field to a context, which in this case is connecting an issue type to a custom field.
But the post is about connecting Field Configurations to an issue type.
Those are two different things. What exactly are you trying to accomplish?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Basically, we created a new custom field, but we do not want it to appear in the sub-task issue type. I'm very new to the admin JIRA world, so I'm probably mixing up a few things here!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Katie
We had a similar issue - not sure it is the correct solution, but our workaround was to create a matching request type (Automation can assign it automatically to the issue type) and then change the fields for the request.
You'll find the settings under request types in the project settings.
Hope this helps - let me know if you need anything further
Thanks, Liam
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.