You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello there,
we are using JIRA and SharePoint in our team and I noticed the following issue:
Currently we are attaching files to an issue that are also saved in SharePoint. (We need them in JIRA to document the progress)
The problem right here is that the attached file is obviously just a copy of the SharePoint file and with that gets outdated very fast and doesn't adopt the changes made in SharePoint...
So is there any solution to link to the SharePoint file instead of attaching a file?
(The only solution I could think of is adding the SharePoint link as a comment but that is a bad solution in my opinion, because it gets mixed up with normal comments)
You can use Power Automate (Microsoft Flow) JIRA connection where if you create a file in SharePoint folder it can parse the name and find the issue in JIRA and add a comment with the shared link.
You can also think of some other way to do it.
I have a similar thing where when a JIRA item is created I create a file with a template content in SharePoint where I add the link of it to the JIRA item comment
Does your Sharepoint allow you to fetch its file by hitting a (fixed) url? You could use web-link urls to that instead of the attachments section in JIRA (maybe with some message text to explain where it is when people want to add new attachments)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Nic,
I am aware of this, but when I use the fixed url of a file you can "only" open or download the file. The check-out options gets lost...
I could link to the SharePoint folder though. I would then have to say which file exactly needs to be opened, but that wouldn't even be that bad, because our SharePoint structure is quite organized. So it might not be so unusual if several files in this folder are relevant for the issue.
The second problem still remains though. Where should the links be added? In the description? I guess that would be the clearest solution.
What is your opinion to that?
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.