Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Linked field in issue gets overwritten when form is editted

Gerben Heinen April 16, 2024

I created a form with a required multiple user selector that is linked to an issue field 'approvers'. The form is used to create an issue. Once the issue is created an automation adds other approvers to the issues multiple user selector and the approval process is started.

Now when someone detects an error in the form, and he\she opens the form for editting, once the form is submitted again, the value of the multiple user picker in the jira issue, is overwritten again by the value which was in the form.

How can i prevent that this value gets overwritten when the form is opened for editting?

Thanks

3 answers

1 vote
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 16, 2024

I think that the issue is related to the rule triggering more than once. Could you share a screenshot of your rule specifically the details section?

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 16, 2024

I suspect you are using the forms submitted trigger. If so, you may need to flag the issue that was created such that a condition can be added to your rule to exit if it has entered on a re-submission. Example, add a label "form-submission" and the add condition to check that labels does not contain that value.

0 votes
Gerben Heinen April 16, 2024

@Joseph Chung Yin en @Jack Brickey thanks for your reply. 

The situation you describe is not what is going on: 

  1. on the form the multiple user selector is used to select a user
  2. the form is submitted, the issue created and the issue's field which is linked to the form's field is filled in with the value on the form.
  3. an automation (or anybody) changes the issue's multiple user selector is changed (person added, person removed)
  4. the form is opened for editing again ('edit form' is selected on the posted form
  5. another field on the form is changed (the form still contains the original value from step 1). This could be a field on the form which is not linked to the issue.
  6. the form is submitted
  7. the multiple user selected of the issue is overwritten with the value in the form, which is the value of step 1 and not the changed value of step 3.

The best way to solve this, to my opinion, is that once the form is opened for editing again, it copies the linked values in the issue and then allows for changes in the form.

Otherwise you should be extremely careful with re-opening a form with linked fields, and it might be better to leave a submitted form closed and require a new form to be created. I noticed that when I attach a new form to an issue, the linked values are copied correctly from the issue.

Thanks in advance.

Gerben

 

0 votes
Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 16, 2024

@Gerben Heinen -

I agreed with what @Jack Brickey suggested,  To supplement to what he stated, if the same form are used for editing after the issue was already created and the form is attached to it, the process will essentially override the actual Jira fields which were setup in your FORM design (via the re-submit action).

One other option that you want to do is to create a different FORM for users which execluded the Jira field linked call out in the FORM, so it will not be overriding the original issue's fields values once the new FORM is submitted.

Hope this also helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events