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.
If it created a link to the JIRA issue, that ticket is updated IMHO. You can put a suggestion to Atlassian to have this changed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How do you "link JIRA issue to Confluence"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.