Duplicate: Bulk Clone Issues & Epics in Jira
Clone Jira issues, epics, subtasks, and hierarchies, edit fields, and duplicate selected issues in bulk with JQL.
ij-solutionsCreate recurring Jira epics, stories, and sub-tasks from saved plans at sprint events or through manual runs.

Regular Work Plans stores a repeatable set of epics, stories, and sub-tasks. A plan can be linked to a Jira project and run at the beginning or end of a sprint, or started manually. It supports recurring Scrum and Kanban work and uses the project permissions already configured in Jira.
Store a set of epics, stories, and sub-tasks for repeated use.
Generate the saved work structure at the start or end of a sprint.
Start a saved plan manually when the structure is needed.
Connect plans to individual Jira projects.
Use the project permissions configured in Jira.
Team leads and project managers running recurring operational or delivery checklists.
Regular Work Plans is paid and cloud-only, while Duplicate: Bulk Clone Issues & Epics in Jira is freemium and supports cloud, server, and data center.
| Name | Pricing | Deployment | Updated |
|---|---|---|---|
| this plugin | Paid | Cloud | |
| Duplicate: Bulk Clone Issues & Epics in Jira | Freemium | Cloud · Data Center · Server |
1,328 plugins in Jira · Project Management
Price distribution: 444 free, 418 freemium, 466 paid
Clone Jira issues, epics, subtasks, and hierarchies, edit fields, and duplicate selected issues in bulk with JQL.
ij-solutionsClones Jira work items with linked issues, subtasks, and preserved relationships.
VilisoftCreate reusable Jira issue templates with variables, pre-filled fields, automation, and scheduled issue creation.
TitanAppsCreate recurring checklists, attach them to Jira issues, generate To-Do issues, and monitor checklist progress in Jira.
SaaSJet«Stop rebuilding the same Jira structure every week. Regular Work Plans saves a template of epics, stories, and sub-tasks, then creates that plan when a sprint starts, when a sprint ends, or when you run it yourself. Build the plan once, attach it to a project, and reuse it for recurring Scrum or Kanban work instead of …»