Community Announcements have moved! To stay up to date, please join the new Community Announcements group today. Learn more
×I made a request in my company to auto fill fields from the EPIC into the child stories. I successfully got a number of fields included in this request. But we could not get the Team field to work. In past conversations, I have come to know that fields can be global or not. So I asked if the Team field was global and found it was not.
We got the following error: Edited work item successfully, however some of the set fields aren't available. Fields ignored: Team (customfield_XXXX).
Does anyone know what needs to be done to resolve this? I verified that they used the correct field.
If you tell me the field needs to be global, can you tell me why our JIRA Admins are reluctant to make fields global?
Hello @Laurie Shimer
Is this a field where you would fill in a value from teams created through the Teams menu?
What type of project does this concern? You can get that information by clicking on the ... button next to the project name in the navigation panel. Both lines of information are important to know.
In the issues being editing by the rule are you able to manually set the Team field through the UI? If you are not able to set it manually, then the Automation Rule also may not be able to set it.
Are the Epic and child stories in the same project?
Do you know if the rule is set up to run against just your project? Or did the admins create the rule to be able to run against multiple projects? Please try to find out the answer to this question.
With that information we will be able to drill more deeply into debugging the problem.
The team field in question is part of the detail fields on the EPIC and stories. Both the EPIC and the story are in the same Jira project. Yes, I am able to manually enter the field via the UI.
I have gotten the Jira admin to successfully auto fill other fields such as the tech lead, QA tester and UAT tester.
My uneducated gut is saying the issue is with how the team field is defined. I have posted other issues with the team field EX when i do a JQL query the team field converts to the team ID so you can't tell what you typed. I was told that the field needs to be defined as "global". I have been unsuccessful in getting the Jira admin to change the attributes of this field in regard to the JCL query.
I am asking the admin if the rule is just for my project, but we are in different time zones and will need a little time.
But if once again the issue is this global attribute, mystery solved. Much appreciated if anyone knows if that is the cause.
regards,
Laurie
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I confirmed the rule is just for my Jira project. The Admin said they are trying to get change the field to be global.
We are getting a successful message but the field is not copying..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Laurie Shimer
Can you share with us the following?
screen images that show your entire rule
images that show the details of the step where the Team field is being set
Screen images showing all the details on the rule audit log generated when the rule executed.
If you are not able to get that information yourself, consider sharing a link to this post with your admin and ask them to post the images.
Without that information we won't be able to debug the problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.