You could ask the user to visit the issue and look, but I'd suspect there's a couple of other problems.
First, why do you need to explain the workflow? That tends to mean it may well be quite complex and hence not that good a process.
Second, if you draw in a workflow diagram and explain it, that's fine, but when it changes, your diagram could easily stop matching the document. It would be better to take a static snapshot and explain that in detail, and then when there are changes, your users will be able to see that there is a mismatch instantly.
I don't need to justify the workflow. When a feature is missing, it's quite common to attack the requestor of the feature as having a not good process.
It would seem quite reasonable for a company to ask to have it's process documented. That is certainly what is driving this conversation.
The suggestion that a snapshot captured in the page along with the explanation of the flow creates the exact problem it tries to avoid. If the picture is "live" then the users can see that it mismatches immediately. If there is a snapshot in Confluence, then the users can read all about the process only to find the mismatch later.
Note: a link to the workflow diagram in Jira would suffice: it doesn't have to be an actual embedded display of the workflow.
Hi Community! I’m Elaine, Confluence Product Manager. You may have read my earlier post about page tree in space navigation sidebar. I'm excited to share another improvement that helps you organize ...
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