-
Suggestion
-
Resolution: Unresolved
-
None
Issue Summary
When using the Proforma field linking functionality, the Jira field is set from the forma form after the issue is created, instead of at the creation time.
This behavior can be an issue in the case where a Webhook is sent at the "Issue Created" event or where an Automation Rule is triggered on that event, as the Jira issue data will contain outdated information for this field.
Steps to replicate
- Create a new Proforma form in a JSM (Jira Service Management) project via Project Settings > Forms, with the configuration below:
- Go to the settings tab of the form, and enable the form for the Customer Portal and select the Request Type of your choice
- Go to the customer portal, raise a new request, and select a priority in the "Urgency" field
- Open the ticket in the Jira facing view
Observed behavior
Check the history tab of the Jira issue that the Priority field was synced with the Urgency field after the issue was created, rather than during the issue creation:
Suggestion
Improve the way the Proforma field linking functionality works by setting the Jira field at issue creation, instead of after.
- links to
- mentioned in
-
Page Failed to load
Form Name |
---|
[FORMDC-796] Improve the Proforma field linking functionality to set the Jira field at issue creation
Labels | New: ril |
Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 980055 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 968504 ] |
Description |
Original:
h3. Issue Summary
When using the [Proforma field linking functionality|https://confluence.atlassian.com/proforma/linking-proforma-fields-to-jira-fields-1087521584.html], the Jira field is set from the forma form after the issue is created, instead of at the creation time. This behavior can be an issue in the case where a Webhook is sent at the "Issue Created" event or where an Automation Rule is triggered on that event, as the Jira issue data will contain outdated information for this field. h3. Steps to replicate # Create a new Proforma form in a JSM (Jira Service Management) project via {*}Project Settings > Forms{*}, with the configuration below: -- Add the template "Report a system issue" -- Click on the "Urgency" field, and select "Priority" field in the *LINKED JIRA FIELD* dropdown on the right side -- SCREENSHOT # Go to the *settings* tab of the form, and enable the form for the Customer Portal and select the Request Type of your choice -- SCREENSHOT # Go to the customer portal, raise a new request, and select a priority in the "Urgency" field -- SCREENSHOT # Open the ticket in the Jira facing view h3. Observed behavior Check the history tab of the Jira issue that the *Priority* field was synced with the *Urgency* field after the issue was created, rather than during the issue creation: h3. Suggestion Improve the way the Proforma field linking functionality works by setting the Jira field at issue creation, instead of after. |
New:
h3. Issue Summary
When using the [Proforma field linking functionality|https://confluence.atlassian.com/proforma/linking-proforma-fields-to-jira-fields-1087521584.html], the Jira field is set from the forma form after the issue is created, instead of at the creation time. This behavior can be an issue in the case where a Webhook is sent at the "Issue Created" event or where an Automation Rule is triggered on that event, as the Jira issue data will contain outdated information for this field. h3. Steps to replicate # Create a new Proforma form in a JSM (Jira Service Management) project via {*}Project Settings > Forms{*}, with the configuration below: -- Add the template "Report a system issue" -- Click on the "Urgency" field, and select "Priority" field in the *LINKED JIRA FIELD* dropdown on the right side -- !StepToReplicate1.png|thumbnail! # Go to the *settings* tab of the form, and enable the form for the Customer Portal and select the Request Type of your choice -- !StepToReplicate2.png|thumbnail! # Go to the customer portal, raise a new request, and select a priority in the "Urgency" field -- !StepToReplicate3.png|thumbnail! # Open the ticket in the Jira facing view h3. Observed behavior Check the history tab of the Jira issue that the *Priority* field was synced with the *Urgency* field after the issue was created, rather than during the issue creation: !ObservedBehavior.png|thumbnail! h3. Suggestion Improve the way the Proforma field linking functionality works by setting the Jira field at issue creation, instead of after. |
Attachment | New: StepToReplicate1.png [ 459826 ] | |
Attachment | New: StepToReplicate2.png [ 459825 ] | |
Attachment | New: StepToReplicate3.png [ 459824 ] | |
Attachment | New: ObservedBehavior.png [ 459823 ] |