Joshua Brock _ Seibert Group_ GmbH Community Champion

Hi @Bailey Lissington and welcome! You've diagnosed the core constraint correctly: in a team-managed project, there's a single board, and board/backlog filters only change what you "see", not what the velocity, sprint burndown, and sprint report are calculated from. Those reports are board and sprint-scoped, so there's no…

Hi @Joshi Vallejo and welcome! Your frustration is understandable, as what you're hitting is a real limitation in the Cloud editor, not something you're doing wrong. The editor treats a list as a single block: any manual indents you set beforehand get stripped the moment you toggle bullets or numbering, and Tab only nests…

Hi @Beth Vinson ... Glad you got the panel off the page! For anyone landing here later: clicking inside the element and using Page Layout → Remove section (as Dan suggested) or duplicating the page (Tomislav's route) are both solid ways to clear out stubborn legacy elements that don't show a selection handle. These usually…

Hi @Noalen Pell ... welcome! Sounds like you figure it out, but great question, as this is a configuration step in Jira Plans that's easy to miss. For custom work item types to roll up estimates to the Epic on the timeline, my suggestions were originally going to be to check two places in your Plan settings (the gear…

Greetings @RAOS12 and welcome to the Community! As the other answers have noted, the due date field on a Feature in Jira's Program Board is a static field, meaning there's no native recurrence engine behind it. Neither Jira Align nor Jira Plans was designed for a Feature to automatically roll its deadline forward on a…

@Pedro Garzon ... greetings and great question! As Asha mentioned, you can use automations as a possible solution. Additionally, if you're open to a Marketplace app, Aura Workflow & Approval might be worth looking at. And in full disclosure, I'm with Aura Apps (a product of Seibert Group GmbH) the company behind it. What…

Hey @James George Lance_ Jr , Cross-space / cross-project automation like this is a known sore spot, in that rules scoped to "for: Parent" generally need the parent and child to live in projects the rule has been explicitly granted access to, and global-admin-level rules can behave inconsistently depending on how the…

@Jamie Knight ... The pain point you're describing (users being able to publish content before an approval is complete) is a real gap in several tools, and it usually comes down to whether the workflow actually enforces page restrictions or just adds a status badge on top of an otherwise unrestricted page. Natively,…

Greetings @Syeda Raeesa Batool ... great questions! These are exactly the right questions to be asking as projects scale. A few practices that tend to make a real difference: Structure epics around outcomes, not features. Epics work best when they represent a business goal or user outcome rather than a delivery container.…

Hi @Haya Bawati ... welcome! Just to add another $.02... To answer directly: JQL-based swimlanes (using portfolioChildIssuesOf()) are still the standard native method for grouping by Feature on a Jira board, and there's no built-in "group by parent issue type" option in the board configuration. The JQL route works, but as…

@Roland Krause ... greetings and welcome to the Community! Confluence Cloud does still have a native Panel macro (as well as the Info, Warning, Note, and Tip macros), so if you're just looking for basic colored callout blocks, those should cover the essentials. You can find them in the macro browser when editing a page.…

@Lana Kelly greetings and great question! Fabio is correct...Confluence doesn't currently support site-wide custom page statuses. Custom statuses are configured at the space level only, so there's no native way to push a status like "Archived" to all spaces from a single admin setting. Your only native option would be to…

@Sabrynna Gibson , sorry for being a bit late in the game ... I see you've already been getting some great guidance. And yes as mentioned, also can't access the instance since it's on your domain. While you're working to sort out some issues regarding those existing macros you've been using, just passing along some…

Hey @Tayler Mendoza As you've found out, this is a known frustration with Confluence's native tab and container macros. Certain macros like the Content Properties Report (Page Properties Report) don't reliably render inside them. The native Expand macro and tab-style grouping macros have this problem with dynamic macros…

Greetings and welcome @Cat Tinsley to the Atlassian Community! A few teams use Confluence as a central HR hub by creating dedicated spaces for onboarding, policies, job postings, and team resources and linking everything from a single landing page so employees don't have to hunt across systems. Natively, Confluence Cloud…

Greetings @ruben_puente Tomislav's summary is spot on. Jira Plans' auto-scheduler assigns work based on team capacity, but it doesn't propagate dependency-driven date shifts the way MS Project does. That gap is tracked in JRACLOUD-88193, and there's no native solution today that I know of. One angle worth considering: the…

@melissa_barton welcome and great question! This is a known friction point in multi-project Jira setups, and the root cause is worth understanding so you can pick the right fix. When your program board links dependencies across multiple Jira spaces, it relies on active sprint references in each of those projects. When a…

Hey @sergio cal and welcome to the Community! The requirements you're describing (cost tracking by team, project, and resource, plus visual resource load management) map closely to what Lean Portfolio Management (LPM) looks like in a SAFe context. That's a space where there are meaningful differences between the options,…

Hi @Shravya Chinthapatla ... Great question! Capacity planning is one of those areas where Jira's native features genuinely fall short, and the right answer depends heavily on whether your org is running a scaled agile framework like SAFe or working at the individual-project level. For individual user capacity, the tools…

Hi @Louis Arkadiusz has the technical side exactly right: Atlassian removed the native HTML macro from Confluence Cloud because allowing arbitrary HTML and JavaScript injection opens serious cross-site scripting (XSS) risks. That's why it's unlikely to come back natively without a sandboxed solution. If you need to embed…

Hi @Raj Purohit Great question — this is exactly the use case Agile Hive was built for. The core challenge with native Jira here is that it has no concept of a Program Increment or an Agile Release Train. You can create sprints and epics, but the PI Planning board — where you see all teams' iterations side-by-side,…

Hi @Justin Wood Glad you found a great solution! For anyone else landing here: Confluence Cloud's native Narrow/Wide/Max page width setting controls the overall content column, and individual elements (tables, images) can be stretched beyond that container through the element toolbar; that's what Kris described so well…

Hi @Kamil Stepien The "Release Package" issue type approach you're describing is a legitimate workaround for the fixVersion linking limitation, and several teams land on exactly this pattern. Typically, you'd put Release Package issues in a dedicated project, then use issue links (blocks/is blocked by) to connect them to…

Hi @Abin Das and welcome! The two answers provided cover the Jira-native path: you'll need Jira Premium or Enterprise to unlock the Work Type Hierarchy settings, then go to Settings > Work Items > Work Type Hierarchy to add Initiative as a level above Epic. One practical thing to be aware of before you make that change:…

Hi @Shital Patel, and a hearty welcome to the Community! The steps John shared are the right starting point... configuring Work Type Hierarchy in Jira Premium (Settings > Work Items > Work Type Hierarchy) gets you Initiatives in the hierarchy. And Danut's point about tracking is worth expanding on, because that's where the…

Hi @Taima Björklund ... hope all is well! You've put your finger on a real distinction: you need a tool that provides information conditionally, not one that collects it. Most form-type apps are built for the opposite direction, so you're right that they feel off for this use case. And Tobias is on the right track…

Hi @Raf Van Marcke and Happy Friday! Yup, you've hit a genuine platform limitation. Confluence's Max width page option controls the overall page container width, but the tables within it, especially those included via the Include Page macro, don't automatically inherit or respect that same setting. The Jira tickets Dan…

Hey @fg8652 ... You're running into a genuine current limitation of Jira, in that Plans operates as a separate navigation layer and can't be embedded as a board tab. Trudy's shortcut suggestion is the best native workaround: a Shortcut link inside the project or space gets it one click away, at least! It's worth upvoting…

Hey Kevin... Yup, understood. The good news: you don't need one source that returns both. Plans takes the union of your sources and rebuilds the Epic→Story hierarchy from the parent links, so the two-source setup is actually the intended way. The rub is that your story source has to be broad enough that no Story that your…

Hey Arnaud, Ok good, that rules out the dates theory. If the stories aren't even showing up in the expanded list under their Epic, the timeline isn't just refusing to draw bars for them, it's filtering them out entirely. So now we're looking for whatever's hiding them. A few things maybe worth checking: * Is the project…