Joshua Brock _ Seibert Group_ GmbH Community Champion

Hey @Kaitlyn Hoban! Arkadiusz and James have already covered the key workaround: creating a new page from your custom template and assigning that page as your space homepage. Regarding the issue where Confluence asks whether you want to replace the existing content but doesn't actually apply the template, that sounds worth…

Hey @Artiom Aleksandrovici, greetings and welcome! I think there are a few different problems wrapped together here, and I wouldn't necessarily try to solve all of them with the same tool. For pages whose original owner has left, Confluence already gives you some useful options. In Premium and Enterprise, Content Manager…

Greetings @Peters, Loes (Lloyds Bank - Nederland) and welcome!! The existing answers do a good job of explaining the Version History side of this. I think the important distinction for your use case is that version history and document approval are really two different things. Version History can show you how a Confluence…

Hi @Tess Baird, Sami's explanation above is spot on. Company Hub's header is the only element that truly runs edge-to-edge, while content in the body still sits within the page margins. So if you're looking for a taller, full-bleed hero like the example you mentioned, that's not something Company Hub currently supports…

Greetings @Alex Smyers I think your read of the current limitation is correct. Jira's native JQL can return work items linked to a **specific** work item using `linkedWorkItems()`. What it can't currently do is take a whole Space as the starting set and dynamically return everything linked to any work item in that Space.…

Greetings @achary_Santosh, and welcome to the Community! James and Rustem have already covered the native options well. If PI is a custom field, filtering a Plan by that field and using "Show full hierarchy" can give you an Epic → Feature → Story view. If you need a more traditional report with fields such as owner,…

@Bevan Williams Thanks for such a thoughtful response! I really appreciate you taking the time to share how your organization is approaching this. One point that really stood out to me was your observation that recurring dependencies are becoming part of regular retrospectives and the Inspect & Adapt event. That's exactly…

Hi @Josue Paniagua Varela ! If you need recurring approval reminders now rather than waiting for this to become available natively, Aura Workflow & Approval supports this use case. Approval reminders can be configured with a recurring cadence, along with the days and time they should be sent. They’re only sent to reviewers…

Hi @Anna Wilson ! The suggestions already shared here point to an important lesson: tools help, but they work best after the team agrees on ownership and what should trigger a review! A practical approach is to start with the content people rely on most, assign a clear owner to each page, and define what happens when its…

Hi @AGASTYA SHARMA ... great question! I think you’re identifying an important distinction: content freshness and knowledge quality aren’t the same thing. A recently edited page can still conflict with another page, use outdated terminology, duplicate an existing source, or have no clear owner. Conversely, an older page…

@Jay Maechtlen ... apologies I'm a little late to the party, and looks like you have some great feedback ... just adding one more if I could. On ownership: the SME who wrote the content is usually the best person to flag when it's stale, but they're rarely the right person to enforce a review cycle or make the final call…

@Harish Babu N Babu greetings and sorry for the delay...not sure if you got what you were looking for at this point, but just my $.02. The closest built-in option (on Premium) is a basic content expiry reminder, but it's a simple notification with no workflow state or enforcement behind it. Broken link monitoring isn't…

Hi @danny_b_tran_disney_com and welcome! I checked this with our development team. Unfortunately, Aura HTML cannot currently pass query parameters or hash fragments between the Confluence parent page and the embedded content. The iframe sandboxing imposed by Confluence prevents the macro from accessing or updating the…

Greetings @Celia Carballea and welcome to the Community! Marc and Danut already covered the native options well ... work item links plus the Dependencies view in Plans, or a Marketplace gadget like WBS to visualize what's linked. Worth adding one thing to that: at the scale you're describing (five tech stacks, several…

Greetings @Deepali Dabholkar ! For the Sprint Performance dashboard, since your team doesn't allocate story points, set your board's Estimation statistic to Issue count (Board settings → Estimation). The Velocity and Sprint Burndown gadgets will then report Planned vs. Closed as plain issue counts, which is exactly what…

Greetings @David Ludwig and welcome to the Community! Viswanathan's approach is solid for where you are today: individual Scrum boards per team (built from saved filters on Components), synced sprint cadence, and Plans for the cross-team rollup. That gets you real per-team velocity and backlog hygiene without forcing all 8…

Greetings @mr john Native issue linking gets you a surprising distance here. Alex's suggestion is solid: keep your "blocks / is blocked by" link types consistent across all teams, and set up a saved filter (or board quick filter) for "is blocked by" so that blocked items surface automatically in standups instead of…

Greetings @Alexander , and welcome to the Community! For a lightweight fix within native Jira: the dependency direction you're describing (Task A blocks Task B, possibly across projects) stores fine as an issue link, but as Mary and Tobi already noted, the built-in Timeline view won't draw those as visual dependency arrows…

Greetings @Faustina Eadie ! To answer your follow-up: in Jira Cloud Premium, "more than one work type per hierarchy level" is configured at the instance level, not per Work Type Scheme. Under Settings > Issues > Issue type hierarchy (the screen Gor linked), you can add multiple work types to the same level (for example,…

Greetings @Tatsiana Gomolko ... At ~15 products with real dependencies between some of them, the four questions you listed (what's everyone working on, do we have capacity, where are the dependencies, can status updates be less manual) are really the same underlying problem: nobody has a single connected view across teams,…

Greetings @Tatsiana Gomolko and welcome to the Community! It's a good sign that you're asking this before picking a tool, the spreadsheet pain usually isn't a tooling problem so much as a missing allocation model. Before evaluating Planyway, Smartsheet, or Big Picture, it's worth first agreeing on how capacity gets split…

Hey @Emma Hall .... welcome to the Community!! From what you've described, this sounds less like a need for a legal e-signature solution and more like a structured policy acknowledgment workflow. Do I have that right? Confluence doesn't provide this natively, but if you're open to Marketplace apps, Aura Workflow &…

Greetings @joshua_k_twumasi ... from one Joshua to another, great point! To answer your direct questions as best the community can ... this is tied to the new unified Timeline UI that Atlassian is rolling out, and several teams are reporting the same regression. The most useful concrete steps right now are to file a…

Greetings @Noopur Agarwal and a warm welcome to the Community here! As you've read, short answer: no, native Jira can't skip a level. The issue hierarchy is a single fixed stack — in your case Initiative > Feature > Epic > Story, and the Parent field only ever connects an item to the level directly above it. There's no…

Hi @Lujain Aljaafari and welcome to the Community! You've already hit the real limitation: components + board filters technically work, but they put the burden on tagging and hand-filtering, and they break down the moment work spans two teams or parent/child links cross team boundaries. A few patterns that tend to hold up…

Hi @Carolyn Harris and welcome to the Community! You've diagnosed this spot on in that there's no native Plans export today that preserves a structured, scenario-aware view. CSV only returns what your current filters and view settings expose, and PNG is a flat snapshot of the timeline. So the structured…

Greetings @melissa_barton and welcome! Yes, the behavior you're seeing is expected: the Program Board in Advanced Roadmaps / Plans only draws dependency strings for the link types it has been told to treat as dependencies. Your defaults ("blocks" / "is blocked by") are recognized out of the box, but your new "blocks…

Greetings @Tam Do and welcome to the Community! Good news on your main concern: adding a new work type at an existing hierarchy level will not break your existing links. In modern Jira, hierarchy behavior is tied to the *level*, not the type name. As mentioned, parent-child relationships now run through the Parent field…

Greetings @Kamila Mucha and hope all is well! Yup, you've hit a real limitation in Confluence Cloud. As James notes, the native Expand macro technically supports nesting per the docs, but the newer cloud editor is unreliable with it, especially once you add a table inside an inner Expand. It tends to break on render or…

Hey @Justine Native capacity planning in Jira Cloud is genuinely thin, and it's thinnest exactly where you are on a Kanban board. The built-in sprint capacity view only exists for scrum sprints (capacity in story points or hours), so it won't help a Kanban setup directly. Given that, your instinct is the right one. The…