Glass Project Documentation for Jira

Export to COnfluence doesn't work

• 

  META-INF KFT

  Hi Daniel,
  First of all, I apologize for the inconvenience.
  While the issue is under investigation and the fix is being implemented, could you please submit a bug report in our support portal so that we can track down the problem and notify you when the fix is out?
  Thank you for cooperating on this one,
  Regards
  Balázs - Product Owner

• 

  META-INF KFT

  Dear Aditya,

  Thank you for your review! I would be curious how could we improve your satisfaction to the maximum (or even beyond) level about Glass? If you have any feedback, feel free to submit a support ticket, or reach us any other way!

  Best Regards, Balázs, Product Owner for Glass products

I have just started using the app but I'm really grateful I did. I am often asked for projects to be created in which I have a form that my team can fill out to request certain things within the project (own workflows etc.). My trouble is after I have created the project based on what they give, the documentation falls a little flat. We also have many of our projects standardised to provide a similar developer experience when switching from project to project. We are often advised to reuse and reduce in regards to project configuration so we wanted a single page that could explain what that standardisation actually looked like. and for us to track changes against these config items. As an admin I feel like this is filling a niche but important gap within the ecosystem. Allowing us to export to Confluence makes it easy to keep this information within the ecosystem and share with non admin users too. When you look at the Confluence export, it even includes good formatting macros like tables and page properties macros so you can better report from other pages. The comparison functionality is great for giving us a chance to see how projects are changing over time and correlate this with productivity changes. I cannot wait to really see how this plays out in the future. However. While the app is great, I would certainly love to see some further improvements within the app: I would like to see whether the export to Confluence would be able to leverage more linking to the admin config specifically (workflow name to actual workflow page in Jira, version pages etc.) or whether we can also include "screenshots" of what the workflow diagram looks like. It would make it easier to make we were going to the config item that mattered. It would be really cool if we could schedule the Confluence exports & updates to pages to be made as almost a 'recipe' so documentation is always kept up to date rather then relying on manual effort. It would be really cool if we could almost checklist the items we wanted in the export. That way if we wanted to ignore things like components or versions we could. It would be even cooler if we could customise the order of the confluence export. Underneath the general information - under the last created issue box - it would be great to include the date and created time of that issue. It would be great if the Confluence export made more use of the Confluence macros we have all grown to love. Things like - date macro, status macro, '@' users. While this may seem small. Confluence stands out from other applications because of macros. So we should leverage these wherever possible. Thanks for the app and keep up the good work.

Thank you for creating this tool! It fills a critical niche for us in being able to document and compare JIRA configurations to support quality validation requirements. The Snapshot functions seems to work, although I need to explore the compare functions further. Export to PDF works, but I have not so far been able to export to a Confluence page (there’s a problem w/ access rights to Confluence – although I thought I’d granted all the permissions needed).

It is no secret that as one's Jira instance grows with sophisticated and complex configurations, the need for proper process documentation and audit checks becomes an essential part of of maintenance and scalability. The downside is that this often requires large amount of administrative efforts. Glass Project Documentation for Jira has helped reducing a big chunk of administrative burden. As a result, we're able to invest that into other areas that need our focus and energy!

• 

  META-INF KFT

  Dear Hamza,

  Thanks for the kind words, feel free to submit new ideas or vote existing ones at our Ideabox :)

  Best Regards, Balázs - Product Owner for Glass products