I'm currently using the Forms functionality on my JSM instance and have a need to export forms as PDFs for printing. When I do this now, it does not show anywhere on the form what this issue key of the form this pdf was generated from, it only shows the issue key in the file name. Is there an easy way to just show the issue-key on the form so when it is printed there is good traceability to the issue it was printed from?
Thank you for your help.
Christian
@Christian I found a workaround while Atlassian doesn't release this feature, I basically created an automation that is triggered when a work item is created, then this automation edits the form's condition from submitted to open for edit:
Then I added an action to edit a custom field called "key" (here you can use whatever name you want, as you will need to create this field and add it to the forms, as this field will only serve to capture the item's key), and for this you will use the smart value {{issue.key}}
Then the automation should change the form's status to submitted
This is the result:
This feature isn't available. There is a feature request for the same, tracked under:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Christian I am not aware of any delivered feature that would provide this functionality. I think you would have to create a custom field that would be linked on the form and then could be updated through automation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.