Search Option for Jira Integration

Users currently scroll through extensive dropdown options in Jira, which can be frustrating and lead to errors.

Main Solution:
Add a search bar to the Jira dropdown to allow users to quickly find and select the desired option. I think this will save time, minimize selection errors, and enhance the overall user experience.

————————

Additionally, Ping Identity shared the following feedback for consideration:

Jira Location: Limit the Jira option to the Menu section of the Project only, rather than making it available question by question or section by section.

Having too many areas to add Jira tickets could lead to duplicate or unnecessary tickets being created.

Jira Creator Field: Include a User drop-down list in Responsive for the Jira Creator field, with email addresses associated with users for easier selection

Find more posts tagged with

Under review

Status: Under review

Comments

Bagavathy N

@catelyn : We have picked this idea of including search to dropdown for analysis. Will analyze and keep you updated on the findings and next steps.

Meanwhile, We see that you have added a new feedback,

Additionally, Ping Identity shared the following feedback for consideration:

Jira Location: Limit the Jira option to the Menu section of the Project only, rather than making it available question by question or section by section.

Having too many areas to add Jira tickets could lead to duplicate or unnecessary tickets being created. "This one seems like a very custom ask for the customer"

Jira Creator Field: Include a User drop-down list in Responsive for the Jira Creator field, with email addresses associated with users for easier selection - "Can you add more context on why they need this?"

cc: @Herthik / @Darshan

Catelyn

Hi @Bagavathy Thanks for your thoughts!

Location: Yes, the client is aware this is a niche request, but I do believe there’s merit to it.

Creator: In addition to the tediousness of typing out full names, some clients have entered things incorrectly or left the field incomplete. Since this field isn’t required, it’s easy for errors to occur. Perhaps, instead of emails, we could consider using User Names? I understand this might be a bit of a stretch, and we may need to think through the request further. I can revisit this with my client during our next cadence.

Catelyn

Update: I did meet with PingIdentity and they did share that their users weren’t including their email addresses or easily searchable usernames, like their full names, making it difficult for the GRC team to identify and reference the right ticket owners.