Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,301,411
Community Members
 
Community Events
165
Community Groups

In the issue collector widget, can we prepopulate some fields and make them read-only?

We are implementing a "submit ticket" system in our application. We are looking at using the issue collector widget to allow end users to create tickets, but if there is a better way to accomplish what I'm describing below, we are definitely open to suggestion.

What we'd like to do is have a few custom fields in the template to automatically collect certain information about the user's environment. We have figured out how to populate the fields, but we also need to make them "read-only" for the end user. Is this possible with the issue collector? If not, what is another approach we can take?

1 answer

0 votes
Dave Mathijs Community Leader Apr 26, 2022

Hi @Jessica Ordoyne welcome to the Atlassian Community!

When configuring the Template of the 'Issue Collector Form', you can set a default value but it won't be added to the form as the default value is already set and cannot be changed by the customer.

The following custom field types can be used: Date Time, Radio Buttons, Multi-Checkbox, Multi-Select, Number, Select List, URL field, Version Picker, Cascading Select, Project Picker, Single Version Picker, Text Field, Free Text Field

Other fields cannot be displayed to anonymous users.

Hi Dave, thanks for the response and the welcome!

I appreciate the info, but that's not quite what we're trying to accomplish. We don't want the fields to get populated until the user starts to create the ticket. These values will be different for each ticket created. We want our application to populate the fields and then display them to the user, without the user being able to change them.

Here's our intended workflow if this helps clarify:

  1. The user is logged into our application
  2. The user clicks "create ticket"
  3. In the background, information about the user and their session (such as username, organization, current page) is collected. This info is loaded into corresponding fields in the issue collector form.
  4. The user is presented with a modal containing the widget for the issue collector. They can see the fields containing the info collected in step 3, but they cannot edit those fields. Other fields like summary, description, etc are presented. The user can edit these fields as normal, and then submit the ticket.

Is this flow possible in JSM?

Like Raychelle likes this

Suggest an answer

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

Improving the Create Issue Experience in Jira Service Management Cloud

Hello everyone!  We are very excited to announce some much needed changes to the issue create experience in JSM (the blue "create" button) at the top of the screen.  We have just starte...

304 views 15 11
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