Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

is there a way to set default assignee from jira issue collector?

hi community!

im looking for if there's a way to set default assignee from jira issue collector?

1 answer

0 votes

Hello @Ming.Il.Li ,

The issue collector itself cannot allow the user to select the assignee of a ticket. And this stems from a limitation covered in the  "Setting field values from JavaScript" section covered in "Customize the Jira issue collector" noting that while most fields can be set:

Setting field values

The issue collector gives you the option to set field values for any of the fields on the issue type.  This is done by adding the property fieldValues in the global object ATL_JQ_PAGE_PROPS. There are different methods for setting default values for different field types.

It discusses the limitation in the Assignee field as a user must be loged in to perform a permissions check and verify if they are allowed to set teh assignee via the project permissions:

Restricted fields

Some fields that require a user to be logged into Jira cannot be set through JavaScript. Assignee is an example of a field that cannot be set via JavaScript.

So there are a couple approaches tyou can take here, the first would be setting the default assignee in the project by going to Project Settings > Users and Roles, and choosing to  assign as the Project Lead or Component Lead the project lead is set under the project settings > Details page and the component lead is set as detailed in:

With the project lead all issues will be assigned to a single user, or using the component you would create various components and set a lead to each the on the issue collector choose a custom form adding the components field to the issue collector so that when the user fils out the form and selects the desired component the issu will be assigned to the user set as that component lead on creation.

Asan alternative approach would be to look at setting up an automation rule to auto assign the issue as covered in:

You could also set this up to use a component or a custom field as your unique identifier to act as a condition.  I am using the issue type as  the unique identifier in an example a s a simple way to tie this togather is to set up the issue collector with a speciffic issue type and use the issue type as your Automation Condition  using a JQL query like:

  • When:
    • Issue created
  • if:
    • issue type = CollectorFeedback
  • Then:
    • Assign isssue
    • Choose desired assignee

Regards,
Earl

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Software

👋 Looking for 15-20 volunteers to test Atlassian training content

Hi everyone! Are you interested in beta testing Atlassian University’s newest (unreleased!) training course? We’re looking for 15-20 volunteers to test our newest training course, Basic reporting...

467 views 19 23
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you