Comments
-
Hi Ashley! I sincerely believe documentations and education are key in bringing current (and future) users on the same page and governance/best practices. Documentations are often a bore, for both the creator and the informed. However, even linking your Jira Service Desk (or Jira Service Management now) to your support…
-
Hi Vaishali! There is how our team does prioritization, and there is how other teams at Twitter do it. Our permissions are set-up so that any Jira users within our instance can create filter and create Scrum/Kanban boards at will. This means the burden/creativity of the prioritization is in the hands of the creator and…
-
I found that as the engineers/implementers of new features on Jira, Confluence, etc., we immediately celebrate the victory upon shipping. As mentioned during the AMA, I think it's crucial to have retros involving major stakeholders to really be introspective and get feedback from external teams. Despite the documentations…
-
Prior to the Jira Data Center implementation, we had to resolve the Jira Service Desk (Service Management now) licensing issue due to how significantly the licensing/cost model changes from Server to DC for JSM. We were on the "unlimited tier" for JSM prior to DC implementation, and there was no way justifying…
-
Hi Benjamin and Dave! As mentioned during our AMA, we cannot live without JEMH and ScriptRunner :) We actually have done incredible amount of customizations involving the latter, and made requests/dreams of our userbase a reality. We definitely should have purchased Automation for Jira earlier, but we were a bit cautious…
