Repeat issue on schedule, use issue as template. Periodically create sub-task or clone issue
Tired remembering every month or specific period of time about something? Don't repeat yourself every time. Hire Jira for this. Decide when your action should occur and schedule it with custom recurrence.
Take control on repeated issues create date and due date and re-schedule them when they falls on non-working day. Managing non-working days for repeatings also helps you guarantee your SLA in Jira Service Desk.
Repeating Issues add-on introduce new simple way to set-up actions that execute on issue with defined recurrence.
- schedule clone issue
- schedule create sub-task
- schedule execution any workflow on issue, e.g. reopen issue
- schedule actions that generate new issue (clone issue, create sub-task) to repeat issue create date or due date
- set-up relative due date for new issues generated by actions
- use variables in issues generated by actions, e.g. in summary, description
- create exceptions for recurring events with non-working days support
- schedule multiple issues with bulk change
- manage permissions with Jira project roles
- send e-mail notifications
- compatible with Jira Agile and Service Desk
Recurrence rules supports iCalendar RFC and can repeats
- at given date and time
- daily, monthly, weekly and yearly
- every n times
- on given day of week
- by day of the month or day of the week
- 1st or last working day of the month
- ends never, after x times, or on given date
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.
Repeating Issues add-on permissions per project / user is in our radar - you can check current roadmap here. We are very happy that our add-on helps you in work.
Hi Dela De Youngster,
We are glad to hear that :).
If you have any questions or suggestions just create the ticket on https://codedoers.freshdesk.com.
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.
|10 users$10||25 users$40||50 users$110||100 users$200||250 users$460||500 & upAdditional pricing details|
- How does server app pricing work?
Server products and apps are hosted on your servers. Licenses are perpetual and the purchase price include 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 host 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 host product. For Jira Server 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 (50 users) and Jira Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for apps. For versions of Jira Server 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.
- Do you offer academic, community, or open-source licenses?
For server apps, purchase and renewal is half-price if you have an academic license for your Atlassian host product. Server apps are always free for community and open-source licenses.
For more details about qualifying for special licenses, see here.
- Can I extend my free trial?
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 host 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.
codedoers is an Atlassian Verified vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.
Version 0.15.4 • Jira Server 7.0.0 - 7.10.1 • Released 2018-06-06
- Resolved date is equal with created date when there is default resolution setup in Jira
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new add-ons from the left-hand side of the page.
- Locate Repeating Issues via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Repeating Issues. You're prompted to log into MyAtlassian. Repeating Issues begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Jira instance.
To find older Repeating Issues versions compatible with your instance, you can look through our version history page.