Hi @Matteo Pacenti
Short answer: an automation rule would need to directly monitor the linked Delivery Tickets to do this, or not use autofill.
My experimentation shows some things about the autofill feature of JPD:
- It does not actually change the JPD field
- It is a display-only feature in the UX, likely implemented with the app code
- This may be confirmed by making a field autofill, changing a linked Delivery Ticket, and then using the REST API to check the value of the field stored in the cloud.
- And because the field does not actually change, an automation rule cannot be triggered
For your scenario, there are a couple of possible workarounds:
- Continue to use autofill, and...
- Use autofill for the display of the field, precisely note how the field is configured, including the source from the Delivery Tickets
- In a multiple-project (or global) scoped rule, monitor any work items which are linked to Ideas and which have a change in their relevant fields
- Use automation rule logic to determine what the expected value is in the Idea. Please note well: this is brittle solution because we are guessing how autofill is implemented.
- Branch to the Idea, and add the comment
- Do not use autofill, and...
- In a multiple-project (or global) scoped rule, monitor any work items which are linked to Ideas and which have a change in their relevant fields
- You decide how the Idea should be updated, and...
- Branch to the Idea to actually update the field, and add the comment
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.