Olga Cheban _TitanApps_ Atlassian Partner

Hi @Drew Wilson ! The permission angle is already covered above, so I will not repeat it. Worth adding a different option, though, in case the cleanup keeps coming back. Cloning copies the source work item, so you inherit whatever was on it, including attachments left over from a comment. For work you repeat often, like a…

@Catarina de Souza Ribas hi! Building such a flow in automation is possible, but it can get fragile, as you've seen. Jira rules don't always handle automations well when several levels of hierarchy are involved. If the goal is a repeatable task with the same subtasks, using a work item template is often steadier and the…

Hi @Booking Commerce ! I agree, keeping the PIM as the source of truth and using Jira for the work around it makes sense. The part worth solving on the Jira side is the process itself, because the same sequence repeats for every product. Enrichment, copy review, media approval, translation, technical verification,…

Hi @Team Creatricx ! Managing a distributed team is trickier than managing an on-site one, but it works well once the process is set up right. At Railsware, our parent company, the team works from over 30 countries. Here are a few core practices that we use: Default to async and skip the call whenever a written message…

@King_ Lee Hi and welcome! Out of the box, Jira clones issues one at a time. There's no native button to clone several issues in a single step. You can bulk-edit existing issues, but bulk cloning isn't really a built-in feature. If you often recreate the same set of issues, our solution might be a better fit than cloning:…

Hi @Troth_ Stefanie ! I'm not sure I understand your use case and restrictions entirely, but I have a suggestion that might be helpful, I think. I would say doing it with Jira automation rules can get a bit overcomplicated quickly. In our team, we have a similar use case where we need to generate a regression testing task…

Hi @AS ! It looks like for your use case, a viable solution would be to set up automation that is triggered manually. This means you set up a Jira automation rule / flow, but select Manual as the automation trigger, but select manual as the automation trigger. Here's an example of what a rule can look like: Then you can…

Hi @Mark stewart ! Jira has a lot of features that allow you to prioritize your work in different ways and track progress. This includes: priority fields backlog ranking JQL filters reordering tasks on the Jira board, and more. I covered this topic in detail in my article, Your Guide to Jira Prioritization 2026, so it…

Hi @Kranthi kumar Girri ! Actually, using a text field for acceptance criteria might not be the best way to manage them in Jira. Acceptance criteria work well as clear, checkable statements rather than one large text blob. In our team, we manage acceptance criteria in the form of a checklist that is added directly to Jira…

Hi @kshridvipa7878 ! Everything on your list is standard configuration, so the main thing is doing it in the right order. Build the two workflows first, then create a single workflow scheme that maps each one to its work type. Sub-tasks are a separate work type as well, so decide whether they follow the Story workflow or…

Hi @wedding planning checklist ! Planning a personal project in Jira is a great way to stay organized, but it is easy to overcomplicate the setup. For a personal project, keeping your hierarchy simple is usually best. Creating separate Epics for major phases with Tasks underneath works well. To track dependencies, you can…

Hi @Kim Wright ! You are right, a filter returns a flat list, so the Epic > Story > Sub-task structure disappears even when every level is in the results. JQL decides which work items come back, but it has no say in how they are displayed. There are two native options that give you the nesting: The List view in your…

Hi @luckybydfi Organizing security and risk documentation is a common challenge, especially in highly regulated industries like fintech. A best practice is to separate static documentation from actionable tracking. You can use Confluence as your "source of truth" for policies, guidelines, and educational content. Creating…

Hi @PgM Innovations Support Team ! That's a good observation and a common issue for agile teams. Sometimes the sprint looks fine on story points, but the actual availability doesn't match the planned scope. I covered this in detail in my article Jira Capacity Planning: How to Plan Team Capacity Without Premium. Here are a…

Hi @Saleha Mubeen ! Thanks for your comments; these are the right questions to ask. For measuring gains, it's best to keep it simple. Before you roll out MCP, track a few things: how long work item creation and updates take, and what the cycle time is for routine admin work. Check the same numbers after a few weeks, then…

Hi @Olivier_OSTConsulting ! Thanks so much for your feedback and for the thoughtful additions! Just a small note: we actually refreshed this article in 2026, so the coverage is current. All the information about native cloning, Automation for Jira, and Marketplace options is up to date. Even if some UI changes might not be…

Hi @Kathy Shaffer ! I've noticed that recently Activity Streams are displaying the original summary of a clone and not the updated summary. I must say this is actually by design rather than a bug, even if the behavior looks strange. Activity Streams show a chronological log of events. Each entry captures the state at the…

Hi @Ruby.Nangia ! Thanks for sharing this. UI changes can be genuinely disruptive when you're used to working a certain way. The best place to send this feedback directly to the Jira team is Atlassian's public issue tracker. You can search for existing suggestions about the recent interface changes and add your vote. Or…

Hi @Christopher _Berry_ Dunford ! Thank you for your question, it's always important to clarify such details! I've just double-checked this again, and actually, native cloning of an epic does clone its child work items/child issues even without automation. Here are screenshots that illustrate this. I hope this helps!…

Hi @Albie Sparv ! Managing onboarding across multiple systems like JSM and BambooHR can definitely get overwhelming as your team grows. To handle the integration with BambooHR (creating employees and syncing data), most teams use Atlassian's native Automation for Jira combined with webhooks, or an external integration…

Hi @Ggy ! Setting up Jira for legal and compliance tracking is a great way to keep your startup organized. For non-software teams, it's usually recommended to create a dedicated Business project in Jira. You can set up custom issue types like "Tax Filing" or "Annual Return" and add custom date fields for statutory…

Hi @Kathryn Lee ! Yes, this is possible, and there's a way to do it without boilerplate stories cluttering your backlog. Native Jira doesn't have a story template dropdown built into the Create form, and it doesn't allow you to create templates for stories and work items in general. However, this can be done with the help…

Hi, @Mark Revely ! Setting up recurring maintenance tickets makes a lot of sense. You don't want to remember to create the same generator checks by hand every time. Native Jira Service Management doesn't create tickets on a schedule out of the box. You'd normally set them up manually or lean on automation rules for each…

Hi @Nicoleta Mircea ! Pulling audit evidence together by hand is indeed painful, and you're right that it eats up days. Auditors usually want to see that each change followed a consistent, documented process. Native Jira keeps the history and transitions, but it won't package them into a clean evidence pack. One practical…

@zoltanersek _outpostlabs_dev_ it's a separate work item called Retrospective, and it's assigned to the team lead who moderates retro meetings. it's only closed when everything is either completed or transferred to the next Retro work item - pretty much like with any other task. apart from that, each team member has their…

Hi there, @zoltanersek _outpostlabs_dev_ ! I can share what works for us and what another team in our organization does differently. Example 1 We run our retrospectives in Confluence. Action items go at the end of the retro notes document, and yes, each item has a clear owner. We then review these items at the end of the…

Hi @Golden Glow Cleaners ! Here are a few practices that help keep things organized when multiple teams share one Jira instance. Use separate projects per team. This keeps workflows, permissions, and field configurations isolated. Teams can adjust their setup without affecting others. If you need cross-team visibility,…

Hi, @Gretchen ! That error usually points to a mismatch between the issue type or field IDs in your rule and what the target project actually supports. Automation rules that hard-code type/field IDs tend to break when the project setup differs even slightly. This can also be a timing issue, as the others pointed out…

hi @Jira user From what I know, even on Jira Premium, custom hierarchy only lets you add levels above Epic, not below. So Epic → Story → Task as a native hierarchy isn't really achievable. Sub-tasks are the only built-in way to break a Story into smaller work items, and they're a fixed level with no further nesting below.…

@Swathi Acharya, if I remember correctly, custom hierarchy on Jira Plans only allows you to add new hierarchy levels above epics, not below. Or has it changed recently?