nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Customer portal - allow customers to attach documentation when transitioning to a status

Allie Stewart

Our customers do their UAT and report defects back to us using the Service Portal. The workflow gets the issues into a "Client UAT" status and notifies the client.

For their testing, they can transition the issue as "Client UAT Approve" or "Fail UAT". If they "Fail UAT", they need to be able to tell us their repro steps, the environment and attach supporting screenshots or other documentation.

Out of the box, Jira does not have this functionality and only provided a very simple comment box on transition. There is a feature request out for this functionality already, but I can't wait years for that.

I'd like to provide a form or custom screen or something for the customer to populate on "Fail UAT" transition. I've tried to create a form to collect the UAT Defect data and allow attachments, but this form has to be on the request all the time. In other words, I can't just have the form show up only when they transition "Fail UAT".

Does anyone have any suggestions or experience with this situation to collect more than just a comment when the customer transitions on the portal? Any ideas/help would be greatly appreciated.

Thank you.

Accepted answers

John Funk

Hi Allie,

Are you using the standard approval process built in to JSM to determine UAT Approve or Fail?

If so, one option might be to have an interim status before the Approve/Fail status. You can have the same transition names - Approve or Fail, but then add a transition screen to the Fail transition that includes fields on the screen and Validators for Field Required. Then, then it successfully transitions, you can move it on the appropriate status. So, you are in effect bypassing the built in process.

All comments

John Funk

Hi Allie,

Are you using the standard approval process built in to JSM to determine UAT Approve or Fail?

Allie Stewart

I'm not using the built-in approval process. I'm not sure how I would set the Approvers because it would different for each customer, but they all use the same workflow. I would have to ask the customer, upfront, who would be testing these issues, and I don't think they know that. Nor do I want them to have to set this manually. Lots of room for error. Unless I'm not thinking about something easier.

But let me play around with the approval process to see if I can get that transition screen to pop up and if I can figure out a way to capture the "approvers". Thanks for the suggestion!

John Funk

Yeah, if you can populate another field with a user value (the customer would NOT be able to do that), then you should be able to copy the user into the Approvers fields.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management