{"id":10900,"date":"2023-06-26T07:19:33","date_gmt":"2023-06-26T05:19:33","guid":{"rendered":"https:\/\/actonic.de\/?p=10900"},"modified":"2023-06-27T09:56:21","modified_gmt":"2023-06-27T07:56:21","slug":"breaking-down-silos-at-work-with-jira-snapshots-for-confluence","status":"publish","type":"post","link":"https:\/\/actonic.de\/en\/breaking-down-silos-at-work-with-jira-snapshots-for-confluence\/","title":{"rendered":"Breaking Down Silos at work with Jira Snapshots for Confluence"},"content":{"rendered":"

[vc_row][vc_column][vc_column_text]My team lives and breathes in Jira. But, to tell the truth, I also know that Jira is not everybody’s sweetheart. Especially for newcomers. For some people, it takes time to warm up to Jira and until they do, the prospect of working in Jira may be terrifying.\u00a0<\/span><\/p>\n

For project managers, this fact can be a time waster, because they are the go-betweens. They can\u2019t afford to live in a Jira bubble and assume that executives will on a Jira link and get the information they need. They are the ones who make cross-functional collaboration work, so they require stakeholders to know what is happening.<\/span><\/p>\n

The learning curve to efficient use of Jira is one siloing factor. The other elephant in the room is that Jira license costs add up. Many organizations allocate them to people who use Jira all the time. So, developers or IT will have them, HR team won’t.<\/span><\/p>\n

 <\/p>\n

Then how to remove the Jira silo?\u00a0\u00a0<\/strong><\/p>\n

What you need is to share Jira information with stakeholders that are not on Jira. To achieve that, you can take one of these approached:<\/span><\/p>\n

    \n
  1. Status Meetings: this certainly is the traditional option. But why use them to review one by one every single Jira issue? It is a wasteful use of precious time together. Wouldn\u2019t it be better to use meetings for problem-solving and brainstorming?<\/span><\/li>\n
  2. Export Jira data to Excel or other formats and share as files on a shared location. This is a common practice.\u00a0<\/span><\/li>\n
  3. If Confluence is your intranet, then <\/span>Jira Snapshots for Confluence<\/span><\/a> solves the problem.\u00a0 With one click, it captures Jira data so that it can be shared with everyone with access to Confluence (even if they do not have a Jira license).<\/span><\/li>\n<\/ol>\n

     <\/p>\n

    How to create stronger Jira and Confluence integration to break silos at work\u00a0<\/span><\/h2>\n

    If Confluence is your internal public square, then project managers should use the Jira Confluence integration to their advantage. Confluence is where they share the project information that is useful to stakeholders. Sure \u2013 the development team has Jira \u2013 from the roadmap to the board to the velocity charts. All very useful tools when you are a developer, a scrum master or an IT support person. But if you are the executive interested in budget outcomes or a marketer waiting for a feature, you just want to see a succinct status for the issues that interest you.\u00a0<\/span><\/p>\n

    Confluence has a native feature that provides that: Jira Macro. It displays Jira data in Confluence pages. Alas, Jira issues are shown only to users who have Jira licenses.<\/span><\/p>\n

     <\/p>\n

    So, how integrate Jira with Confluence to share Jira data with users who have no Jira license? <\/span>Jira Snapshots for Confluence<\/span><\/a> solves this problem (and some more). With this App, project managers can show non-Jira users exactly the issues and fields that are useful to share. The data is a static capture of Jira data at a moment in time. The snapshot app stores the data in Confluence. Hence, all Confluence users share exactly the same view.<\/span><\/p>\n

    The app has a few more sparkles, which make it a favorite for project managers:<\/span><\/p>\n