Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Hi,
I have a scenario where I want to be able to print out a Dynamic Form as a PDF, and at the end of the form show the person who submitted it and the date it was submitted. This is necessary as we need to prove who made the request and when. Yes, I can see this info in the Jira issue, but if we need to print and send this out to anyone that info is lost. Any type of approval form or contract would require this.
To do this, I thought as the Reporter field in Jira should hold the correct value for the person filling in the form, I could introduce this at the very end of the form, along with a date field.
However, the reporter field does not populate automatically. Naturally, the Customer can set this field, but it would be nicer to have this set automatically when the Customer is filling in the form via the portal.
Is there any way to do this as I can't see that it's possible?
It would also be nice if I could lock the field down if it could be automatically filled in so that the Customer could not change it.
Am I missing something very easy as both don't look to be possible, but I thought I'd ask!
Thanks in advance,
Tony
Screenshot for reference:
It is my understanding when one uses FORM design for issue creation in JSM, the reporter field will always be automatically populated as the one who submitted the FORM and created the issue.
Have you also setup the FORM design for your process where not only the issue is created, but the FORM is also added as an attachment (pdf) to the issue itself?
Once you setup the designed mentioned above, you will see the FORM pdf attachment, where it will contain the reporter and time the issue was created. You can then share the PDF attachment to other users as needed.
See example of the PDF extraction of the reporter/time information below -
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Technology Applications Team
Viasat Inc.
Perfect, that should give me what I need :)
Many thanks, Joseph.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm not fully understanding the print need, but putting that aside for a moment, every request created through a service portal should have 5 required fields:
There are only 2 ways I can think of this not being the case is
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What can I say, sometimes you need to produce a hard copy for legal reasons.
As I am using forms in a Jira Service Management all the fields above do not appear on the form unless you add them, and then items like reporter do not automatically fill in.
What Joseph has replied should be good enough for my purposes.
Many thanks :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Journeys is a brand new feature in Jira Service Management that helps you streamline various processes in your organization that may cross multiple departments, such as employee onboarding or off-boarding that require action from different teams. ✨
Join the EAP →
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.