Viktoriia Golovtseva (TitanApps) Community Champion

Hey @Kelvin Chua thank you for the great question, that's the one we'll explore and test further in the next months. As for now Rovo has some governance building blocks, but configurable per-action approval gates aren't one of them today. Here's what does exist: * Permission inheritance. Per Atlassian's docs on Rovo agent…

Thank you @Mia Tamm _Simpleasyty_ we're always trying to experiment with all new things Atlassian has and agents were definitely a priority, before you test something you cannot really understand its value so we'll do our best to share more practical use cases in future. I really appreciate your interest 

Thank you @Ashik Muhammed _ AIO Tests for the insightful comment. Indeed checkboxes are not enough in many cases 

Hi @Christopher _Berry_ Dunford, you're right — thank you for pointing this out. The wording conflated two different things. Here's the accurate picture: - Native Clone on an Epic copies only the Epic. Its child Stories and Tasks aren't included, because those aren't Sub-tasks — they're separate issues linked to the Epic…

Hi @Ariel Yadin _ Bazz OKR , thanks for such a thoughtful comment - the "one level above epics, not three" advice is spot on. Deep goal hierarchies look impressive in planning decks but collapse under maintenance overhead. Most teams are better served by a flat linking layer they'll actually keep updated. One update worth…

Hi @Matt Smith , great question. There's no single "off" switch for story points across all of Jira, because they live in two separate places: the field on work items and the estimation setting on boards. To remove them everywhere, you need to address both. 1. Hide the Story Points field from work item views…

Hi @Kevin miller! It's worth knowing that Jira does have a native checklist option now, called Action Items. You can add them inside the description of any ticket. Each item has a checkbox you can tick off as work gets done. For simple to-do lists, this can be enough. We have a full walkthrough here if you want to see how…

@Evie Z_ thank you for the update on external links I'll keep this in mind for future posts

Love this ❤️ I have a similar “how did I not know about this before?” story from the other side of the world. A few years ago I moved to Romania and someone casually mentioned “you should see the Christmas market in Craiova, it’s surprisingly nice.” I had to google the city first. It felt like one of those small places you…

Hi @Scott McDonald You can: Rename hierarchy level names (e.g. rename “Epic” level to “Feature”). Add extra levels above the Epic level if you’re on Jira Cloud Premium / Enterprise (for things like Initiative, Solution, etc.). You cannot currently insert a new level between Epic (L1) and Story (L0). That’s a long-standing…

@Darin - Opus Guard thank you Darin. I cannot agree more. That is why Smart Checklist for Jira is now also compatible with Atlassian Government Cloud, meaning it aligns with the elevated security, data protection, and compliance requirements expected in regulated sectors. 

Hi @Gabriel Carrillo Welcome to the Atlassian Community. “Fields ignored: Checklist Text (customfield_10xxx). The set fields may be unavailable for this project/type.” That message means Jira could not set the Checklist Text field on the issue you created. In practice, one (or more) of these is true: The field isn’t on the…

Hey @Ihor Mytyuk What you’re seeing usually happens when Jira renders the Description with a format that doesn’t support interactive checkboxes, so the “tasks” fall back to plain bullets. Here are a few quick things to try, depending on your setup: If you’re on Jira Cloud Use markdown task-list syntax exactly like this…

Hey @Scott Stevson Welcome to the community. We at TitanApps faced a similar challenge and opted for standard Task/Sub-task types combined with our tools Smart Templates and Smart Checklist to manage onboarding and offboarding in our team. Templates help us standardize requests for different roles or locations, and…

@Bill Sheboy thank you, made correction in the answer

Hi @Logan Reichert You're on the right track using automation with summary flags like "Mgr –", but assigning users dynamically based on a custom people field like "Manager" can be tricky in native Jira automation, especially across multiple subtasks. If you're frequently creating onboarding tasks and assigning them to…

Hey @Nimantha Deshappriya Kappetiyagoda Vithanage welcome to the community. You can achieve this in Jira using native automation rules. To create tasks (issues) that automatically include subtasks (keep in mind that tasks should belong to specific epic) you can: Go to Project Settings → Automation Create a new rule with:…

Hi @Mahnoor Arshad You can definitely achieve this behavior, but instead of writing a custom script, I’d recommend a more reliable and scalable solution using a checklist validator. If you try Smart Checklist for Jira, you can solve this elegantly by replacing the sub-task with a mandatory checklist item and then applying…

@__ Jimi Wikman thanks for rising this question. Having a known, stable velocity in story points for the team, and a total story point estimate for a feature/initiative/project, you can easily translate these into meaningful time/financial estimates for external stakeholders. That’s what we use for our products. For…

Thanks @Darryl Lee for this discussion. I totally agree that the current handling of checkbox fields in view mode misses the mark, especially for teams that rely on clear visual cues for what’s in vs. out of scope. Seeing only the selected options defeats a big part of the purpose. It hides the full context, which is…

Hello @光野　かおる One option would be to use Native Jira Automation Option You can automatically transition a Story to "Done" when all its Subtasks are closed using Jira’s built-in automation. Here's how: Steps: Go to Project Settings → Automation. Click Create Rule. Set the Trigger: Choose Issue Transitioned → To status: Done…

Hey @Cindy Franklin Welcome to the community! Jira doesn’t support this natively with its built-in checklists, but as the company's representative I would recommend Smart Checklist for Jira to implement it. It’s possible to require that all checklist items be completed before a Jira issue (card) is moved to “Done” or any…

Hi @[deleted] Here are a few suggestions that might help: Can you make "Action Item" the default or sole sub-task? Unfortunately, Jira doesn’t support setting a default sub-task issue type directly in the UI. However, you can hide the default “Sub-task” type from users by: Removing it from the issue type scheme for that…

Hi @Leoš MAREK You can absolutely inject those little GUI-style checkboxes via the REST API by editing the issue’s description field in Jira’s Atlassian Document Format (ADF). Please check this documentation for details. I think that field input format as checkbox custom field should help. When you might want more than DIY…

Hi @SilkeS, Thank you for noting this, sure I've corrected the answer to mention this information.

Hi @Pannha Griff Welcome to the community. It sounds like you're running into a common challenge with Jira’s native automation. Typically it handles work item creation well, but it often struggles when you're trying to automatically nest tasks or sub-tasks under parent issues, specially across multiple levels like Epic →…

Hey @Nancy White If you're looking for a structured way to manage ~20 onboarding tasks across different assignees, I highly recommend checking out this article: Employee Onboarding Template for Jira: Streamline New Hire Integration. It walks you through setting up a reusable onboarding workflow using Jira, along with Smart…

Hey @Eran Roiter This is a common challenge, especially with quarterly planning and larger dev teams. If you're looking to move away from manual tracking and gain a real-time view of how you're progressing vs. expected delivery, I highly recommend trying the free Smart Productivity & Team Performance Dashboard by TitanApps…

Hey @Jesse Allen You might want to check out the Smart Productivity & Team Performance Dashboard for Jira by TitanApps (available on the Atlassian Marketplace). With Smart Productivity Dashboard, you can: View user-level sprint history and performance – see which work items (issues) were assigned, created, and completed by…

Hi @Ikumi Kunikane You're right - Jira doesn’t support pre-filled descriptions out of the box in company-managed projects. If you're looking for a way to create reusable issue templates (including prefilled descriptions, custom fields, dynamic variables, and even scheduled issue creation), I’d recommend trying the Smart…