Hi,
Currently in JIRA cloud this field ' team' is not mandatory/required and not filling it leads to loosing the track of the issue type as we have different teams and their backlog is filtered based on the field 'Team'.
Is there a way to make it required ? As a workaround i thought of using automation to send the reminders to the reporter to fill out this field. But in automation also this field does not appear.
Is there a way to handle this issue ?
Thanks
Harshal
I've verified that the Team field is available in the Field Required Validator, which can be added to the Create issue transition. Could you confirm if you're using a company-managed or team-managed project?
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.
I tried but was not able to find the validator to apply to the transitions. Can you please share with me the steps to do that.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Follow the steps:
I hope it helps
Cheers
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.
The problem I see is when a ticket is being moved between issue types/projects. it won't ask to put the field value (Team), it will just move the ticket. Is there a way we can make "Team" mandatory on issue move as well?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Maciej Dudziak _Forgappify_ - I'm not able to see Team field in Field Required Validator in workflow. It is system Team field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Manish Arya
Did you try to type in the name, dropdown list can be limited?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also, depending on the structure of your organization and projects, you can also set up an automation rule to directly assign a specific team to an issue on creation, edit or move, based on the project location of the issue. What I have done for my organization right now is to automatically set the Team field (based on Team ID) to match the project the issue is created in. By doing this, I know this field will always be automatically filled out for new issues.
The next steps I am then going to create are some rules to update this value based on moving the issues or editing the issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am trying to find a workaround that does not involve transitions. One idea I had was to create a custom field set to required, called "Assign to team". Then I would add a project automation on issue creation to set the "Team" field value to the same as the value selected for "Assign to team". Currently I am setting this up, so I have not confirmed this works, but wouldn't this be a logical workaround?
@Sal I think you could use the same logic with automation for other actions as well, such as moving issues?
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.