This question is in reference to Atlassian Documentation: Configuring Issue Linking
Noticed that when linking to a JIRA issue from Confluence, the 'updated field' in JIRA gets updated too, which a) is unexpected because it doesn't necessarily have anything to do with engineering work per se and b) derails the engineering flow completely because you can no longer trust the updated date field as a data-driven tracker.
I can't answer that question in details as I didn't implement the feature myself. What I can tell is that we have a Jira/Issue Filter macro from within Confluence to reference any JIRA issue (e.g. to build an arbitrary engineering tracker/dashboard). Then, in JIRA, the Issue Links section will be populated by the Confluence page(s) referencing the issue(s). My problem is that the JIRA issue Updated: field should NOT be updated when this happens, because this has no engineering context at all and derail the team's workflow.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs