JIRA must haves
*Tempo - Time Tracking
*Elements (Custom Fields)
*Jira ToolKit
* nFeed
*Dynamic Forms for JIRA -
*Dataplane(Reporting)
*Rich Filters for JIRA Dashboards
*Agile Board Filter(Dynamic Filters)
*Agile Remaining Counter
*Automation for JIRA
*Power Scripts - Script Runner
*Audit Log
*Configuration Manager - Project Configurator
*SAML Single Sign On
JSD
*Extension for JSD
*CSAT Surveys
Confluence
*Scroll PDF Exporter
*Lucid Chart
*Linchpin
*Brikit Theme Press
*Page Tree Creator
I'm late to the game (nice summer vacation!), but I can post my deck that lists the add-ons, although it looks like @Tinker Fadoua did some awesome note taking -- I'd expect nothing less!
Hi @Thad West
I mentioned that it was your hard work as I hate taking credit for something I didn't do.
Always a pleasure attending your presentations! Enjoy your time off!
Best,
Thanks for the post. There are a few on here we are not using and I will check them out.
We also use Adaptavist Script Runner quite a bit in our JIRA environments.
@Bill Tannermy pleasure! It is not the whole list, I did my best to take notes while Thad West was presenting during a recent NOVA meetup.
@Tinker Fadoua thanks for capturing this for the community! I love this.
Something is on the way for the community. I will have it ready tonight. I put it as "in progress" on the Champions Trello Board.
@Tinker Fadouathis is AAAAAAMAZING! Thanks for trying this out and showcasing the benefits of utilizing this space for AUG members who join the event or don't.
Oh!!!! I really didn't do anything I just copied the list that Thad worked hard on putting together. Thank you @Celina Zamora!
If you're using Confluence in more of an enterprise-CMS function instead of a true anyone-can-edit wiki, the one must-have I'd suggest would be some kinda workflow-and-approval plugin. I used Comala Workflows. https://marketplace.atlassian.com/apps/142/comala-workflows
In my case, we were writing and editing FAQ answers for a helpdesk that was speaking on behalf of the US Government, so while we had some latitude in what we were allowed to say, having some consistent, measured responses required that they be reviewed by several people - some folks familiar with policy, some tech writer folks who could edit for clarity and voice, and ultimately the training folks who would see to it that this information was pushed out to the entire call-center. The business rules were
That workflow had four basic paths (depending on who initiated the request) and a more than a dozen states, and was kind of a pain in the ass to implement on the technical side, but from the user end, it turned hours-long content review meetings into a dropdown that showed up in the app that said "you have stuff to review" that people could get to whenever they got to. People clicked on stuff, pages got approved, changes went into production. Huge time-wasting meeting eliminated.
Thanks, Huey. We do FAQ stuff as well for the government. I will check out Comala Workflows for Confluence.
Thanks for the post @Tinker Fadoua
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.