We have a use case where we are using a ProForma form to capture IT Security Review details in a Jira ticket. And without going into specifics, many of the fields in the ProForma form we have linked to Jira Fields for use with Jira automation.
We allow the user or IT Security staff to resubmit the ProForma form with improvements to the original detail they provided, after the ticket is originally created.
However, when doing so, we would like to have in the history log (or even automate an internal comment in Jira ticket) to denote which human user initiated the updating of the ProForma form that is already attached on the ticket.
But what we see right now is that the History log in the Jira ticket will only return "ProFormaJ" as the user responsible for the edit to the linked Jira fields modified in the ProForma form. Also when attempting to automate a comment detailing the initiator of the update to the form, this yields the same result "ProFormaJ".
Using e.g. {{initiator.displayName}} re-submitted the form.
Is there something we are missing? Is there a way to find out the user that re-submitted the ProForma form on this ticket? (since its possible its not always going to be the Reporter)
Thank you
Hi @Matt Lane
Thinking simply, if a lot of the form fields are linked to Jira fields - wouldn't it be possible to identify the user from the Issue History?
If this is suitable (appreciating a user could also update a field directly) - then you could have an Automation rule populate a user picker custom field - Last Updated By - for example...
Would this work in your scenario?
Ste
Hi @Matt Lane
Even if a Jira field is modified through the form?
On the Forms on our instance, when I modify a Jira-linked field through the form, it shows in the History that I modified the field itself directly.
Perhaps a screenshot of an example History would be beneficial here :)
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Stephen,
Here is a brief example of the history when ticket created after initial submission of ProForma form:
And then brief example of history when fields updated after re-opening and having re-submitted ProForma form on the ticket:
Regards,
Matt
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Matt Lane
I can't replicate this functionality - I assume you might have had Proforma already before Atlassian rolled it out as Forms? Perhaps this is the reason?
I'd suggest contacting Atlassian Support for this one, and ask for some clarity around why this functionality might differ between instances.
Let us know if you find a resolution :)
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ste Wright
Yes we did have the ProForma app before the rollout under Atlassian.
That seems to be exact reason. And I found precise reference to this in Q&A.
https://www.atlassian.com/licensing/proforma#
- Look for question: "What changes are there between the ProForma Cloud Marketplace app and the new native form builder?"
So looks like we can look forward to history included records of who updated each Jira linked field in the ProForma form reflecting our users and not "ProFormaJ"... once our existing ProForma data is migrated from app to native version, which since I wrote this question here in the forums, our migration has been scheduled for sometime in April in coming weeks :-)
Hopefully all sorted soon anyways!
Cheers,
Matt
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Matt,
Interesting! Thank you for clarifying this for the Community - hopefully it will help others who also have this question prior to the migrations being completed!
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.