Resources

Reviews for cloud

We just started using this plugin a few weeks ago, and the scrum master that requested it has found it useful.
We made a feature request based on how we'd like to configure the plugin, and the CodeDoers team accepted our request and added it to their next release right away. That's what I call very responsive support!
Dave

We will consider feature with configurable value for cloned issue due date. Currently due dates are adjusted based on original issue dates. Please read How to determine cloned issue due date? on our documentation page.

! UPDATE !

From version 0.7.0 user can more precisely control issue due date with issue duration field when set-up repeating.

Nice plugin and simple UI. It would be nice if we had permissions (both to restrict this plugin to certain projects/issue types and also to prevent certain users from seeing or modifying the recurring schedule). That's useful because a user could accidentally disable a schedule and we'll never know.
A solution for us is to make a new issue type: "recurring maintenance" and then restrict certain user rights around that. But it isn't a perfect solution.

We are sorry to hear that. In our freshdesk support it looks like you have reported:

(1) Problem with required fields during repeating action.

(2) Question how to find repeating issues definitions.

(3) Problem with issues created by add-on that are not linked to agile board.

Tickets (1) and (2) are resolved with soulutions and new add-on versions. For ticket (3) we provide ongoing support trying to reproduce your issue, and it looks like this is not a problem with our add-on at all. Repeating Issues does not support the flow like you described in your last response. We are also open to provide new feature like yours and other suggestions to make Repeating Issues add-on more productive.

Reviews for server

This add-on makes life a million times easier for users. While implementing JIRA and JSD, we had many staff digging in their heels to new processes. This "little" add-on is a big deal and probably the biggest selling point to in getting staff to (grudgingly) embrace change.
Response times to troubleshooting issues are lightning-fast. Seriously, I submitted a ticket and 3 minutes later I had a solution.

Reviews for Data Center

We just started using this plugin a few weeks ago, and the scrum master that requested it has found it useful.
We made a feature request based on how we'd like to configure the plugin, and the CodeDoers team accepted our request and added it to their next release right away. That's what I call very responsive support!
Dave

We will consider feature with configurable value for cloned issue due date. Currently due dates are adjusted based on original issue dates. Please read How to determine cloned issue due date? on our documentation page.

! UPDATE !

From version 0.7.0 user can more precisely control issue due date with issue duration field when set-up repeating.

Nice plugin and simple UI. It would be nice if we had permissions (both to restrict this plugin to certain projects/issue types and also to prevent certain users from seeing or modifying the recurring schedule). That's useful because a user could accidentally disable a schedule and we'll never know.
A solution for us is to make a new issue type: "recurring maintenance" and then restrict certain user rights around that. But it isn't a perfect solution.

We are sorry to hear that. In our freshdesk support it looks like you have reported:

(1) Problem with required fields during repeating action.

(2) Question how to find repeating issues definitions.

(3) Problem with issues created by add-on that are not linked to agile board.

Tickets (1) and (2) are resolved with soulutions and new add-on versions. For ticket (3) we provide ongoing support trying to reproduce your issue, and it looks like this is not a problem with our add-on at all. Repeating Issues does not support the flow like you described in your last response. We are also open to provide new feature like yours and other suggestions to make Repeating Issues add-on more productive.

Cloud Pricing

Server Pricing

Data Center Pricing

Pricing FAQ

Server products and apps are hosted on your servers. This app is sold as a perpetual license, and the purchase price includes 12 months of maintenance (support and version updates).

You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your Atlassian product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

How do I determine my server pricing?

Apps are billed based on the number of users in your Atlassian product. For Jira 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (500 users) and Jira Service Desk (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly. Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.

Can I install this app in a Data Center product?

This app does not have a a Data Center approved version. Only apps meeting a set of performance requirements for large, clustered environments are approved for Data Center.

However, while server apps are built for single-server deployments, many customers successfully install them in Data Center products. If you're using a Data Center product, Atlassian recommends you contact the vendor to determine compatibility at scale.

For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian product, and you're all set.

How can I buy apps for my legacy Jira Server or Confluence Server license?

If you own a legacy Jira Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:

Purchase the app at the non-legacy Unlimited (10000+ users) tier.

Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.