Questions? We have answers.
You can find answers to commonly asked questions below.
Almost anything. The most common ones are numbers, time values, attachments, comments and version dates.
These features are only available on Server and Data Center because Atlassian prevents displaying HTML custom fields in Jira Cloud. We are working on an alternative solution.
Epic Sum Up works well with most other plugins out of the box. This is because we designed Epic Sum Up to be as close to the Jira native functions as possible. We are working on formal integrations with other plugins. Have a specific request? email@example.com
Epic Sum Up provides an analysis of the current state. Longer term reports are not yet available.
See our Jira Compatibility Matrix.
As per our Service Level Agreement Trivial is six (6) hours for a reaction from us and 72 hours for a solution.
While Major is four (4) hours for a reply and 24 hours for a solution.
Note: this is based on business working hours of Monday to Friday 9am-5pm CET (Central European Time) excluding German holidays.
Premium support is also available for an extra cost. With it you get a reply in two (2) hours and a solution in ten (10) hours for mission critical issues.
Progress Bars and Summary Panel
Server and Data Center: Summary Panel and everywhere custom fields can be used.
Cloud: Summary Panel and epic overview report.
Currently we use the built in resolution field for a resolved state which is the Jira default behaviour. This means the status does not affect the completion of the progress. We are working on a more precise definition of done.
Use custom fields. Progress bars can be displayed via custom fields. Add them using the administration issue settings. They can be displayed all over Jira.
Green = Time spent within estimation
Grey = Estimated time
Light red = Remaining estimate time over original estimation
Red = Time spent over original estimation
White (dotted line) = Time spent + remaining time under original estimation
Epics and Containers
An issue that has the function to be a parent to another issue. It is similar to an epic. Every issue can be defined as container.
Three options: epics in containers, containers in containers, and containers in epics. Just activate the “container in container” function in the Epic Sum Up settings.
Epic Sum Up works with a clear assignment of issues. That is why we insist on using either an epic link or a container link.
We request live data so the summed values are not stored at the issue level. Due to the speed of value changes there is no proper solution to index the values which does not impact the server speed at the moment.
In More Detail:
If you want to query on values in custom fields or sort them in issue navigator the value must be stored in the field so it can be indexed.
Our summary values do not store rather calculate on demand. That’s the reason why we cannot search or sort for summed values. If we would store these values, we would force the server to permanently recalculate these values, which leads to a performance issue.
Evaluation and Pricing
Go to the Atlassian Marketplace Epic Sum Up page and select the “Try It Free” button in the upper right.
Server and Data Center can only be purchased yearly.
Cloud can be purchased monthly or yearly. For full details please go to our Pricing Page.
You pay the pricing tier you fall into. Example for the server version if you have 25 users you pay the pricing tier for 25 users (11-25 users). But add one more user, which makes your total 26, and you pay the pricing tier for 50 users (26-50 users).
This is Atlassian policy. This means often when you add a few new users you do not pay extra. You only pay when your user count enters into a new pricing tier.
Our Pricing Page includes a calculator.