We want our constantly changing SharePoint requirements documents to be linked to the appropriate JIRA issue and have any/all updates/changes carried over so that we could avoid duplication of effort as well as everyone see the same information. Which add-on or tool would support what we need? We would like to have our customers go directly to the SharePoint site input their requirement needs and have it carry-over to our JIRA tickets/issues. We really need a one and done process whether it be using JIRA with SharePoint (i.e. JIRA's Confluence, Connector, or even Office365). We love JIRA, but we need 1 tool not multiple tools that don't talk to each other. PLEASE help us. Thank you!
Flo Kistner, Ph. D.
The best solution is to dump Sharepoint and move everything into Confluence. The tight integration between Confluence and JIRA will make it far easier to work with them - you'll have a single source of truth for all your documents (with full revision history), the ability to create issues directly out of Confluence with a single click and reporting out of JIRA embedded directly in the Confluence pages.
If you insist on using Sharepoint, then you're pretty limited - Sharepoint simply doesn't have the flexibility needed to closely integrate with JIRA and pretty much all you can do is embed links into the Sharepoint documents or their metadata, and have simple web links (that will break if things move) from JIRA issues to Sharepoint docs.
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