Habib__Plugio__ Atlassian Partner

Hi @Dieter Guthmann, Not a full replacement, but you can at least get the quick lookup back with a custom search engine in the browser. In Chrome/Edge: Settings → Search engine → Manage search engines and site search → Add. Firefox does the same with a bookmark keyword.…

Hi Abhishek, Most of this is covered natively if you build it on one saved filter. Finding stuck work. Jira keeps a statusCategoryChangedDate field. It records the last time an issue moved between To Do, In Progress and Done. statusCategory = "In Progress" AND statusCategoryChangedDate <= -5d lists everything that has sat…

Hi @Karl Samson The second half of this is covered natively. The Resolution Time gadget plots the average time between Created and Resolved per day, week or month for a saved filter. That is your trend line. Put it next to a Created vs Resolved gadget on the same filter and you have both views. For the team split, make one…

Hi @Howard Wei It's not the Free plan. Dashboards and gadgets work the same there. Two things to check: The search has to be saved as a filter. Running JQL on the search page is not enough. Open Filters → View all work items, run your query, then click Save filter and give it a name. Only saved filters show up in gadgets.…

Not really. Scenarios are "what if" branches of the same plan, not baselines. A scenario only holds the unsaved changes you make in it. Everything you don't touch, including status and progress, is read live from Jira. There is also no side-by-side or variance view, you can only switch between scenarios one at a time. So a…

Hi @Gor Greyan No native setting does this. The time tracking roll-up is one level only, by design. Atlassian says so in the June 2025 update on JRACLOUD-70150: a sub-task rolls up to its parent, and the Epic gets its direct children, but nothing from the sub-task level. "Include subtasks" on the Epic doesn't change that.…

Hi @Richard A. Michaels The likely cause is the subquery inside epicsOf. It has no project clause, so it matches every Story, Task, Bug and Spike created since January 2025 on the whole site. As far as I can tell, the outer project = "MyProject" doesn't narrow it. Adaptavist's docs treat each function call as its own…

Hi @Priyadarshini R Thanks for the screenshot. This is getting into app configuration, so please open a request on our support portal with that screenshot and a short description of the table you want. We'll sort it out there.

Two separate things there: Multiple projects: the Project dropdown is single-select on purpose. Leave it on All Projects and put the projects in the Filter box next to it, e.g. project in (REC, HR). That box takes any JQL, so you can also add created >= -30d there. Table with REQID, Status and other columns: the pivot only…

Hi @Priyadarshini R You don't need a plugin for this, a saved filter and a dashboard gadget cover it. "Who created the profile" is the Reporter field, unless your project has its own Recruiter user field. Start with a filter for the day you want, e.g. yesterday: project = REC AND created >= startOfDay(-1) AND created <…

Hi @Godwin-Rousso_ Justin , A few options, from softest to strictest. They combine, and which mix fits depends on how much friction your teams accept: Make it visible. Keep the maintenance epic but time-box it (one per quarter, named that way) and give it an owner. A dashboard number like parent = MAINT-123 AND created >=…

Hi @Godwin-Rousso_ Justin The hole you've found is structural: Bug sits on the same hierarchy level as Story and Task, and a parent has to be one level up, so a Bug's Parent can only be an epic-level item. For a bug about a story that isn't under any epic there is no valid value, and a mandatory field just makes people…

Hi @Rilwan Ahmed , I mean it is not a well thought pricing policy, is it? It seems they just copy/pasted $0.25 for each bucket. Of course this is my assumption, because of that I suggested to reach the vendor for confirmation.

Hi @sahitya_satrasala Adding people to a board doesn't grant access — board visibility comes from other settings. Check these three things: Project permission: the people need the Browse Projects permission in the project(s) the board pulls issues from. Easiest fix: add them to a role in Project settings →…

Hi @Scott Derderian I'm fairly sure that $25K is a pricing mistake on the listing, not the intended price. I'd email the vendor and ask them to correct it — and while you're at it, ask how the app performs at your scale.

Hi @aokeeffe_guidewire_com , Unfortunately there's no native setting for this — the Sprint field stores every sprint the issue has been in, and CSV export writes each value to its own column. Two workarounds: Spreadsheet formula. The last non-empty Sprint column is the current one. In…

You've got the windows right: AFTER -90d is May 27 through today, BEFORE -90d is everything up to May 27. The missing piece is what CHANGED checks. It doesn't look at when the last change was — it asks "does at least one status change event exist in this window?" So "status CHANGED BEFORE -90d" = "has at least one change…

Hi <a href="https://community.atlassian.com/forums/user/viewprofilepage/user-id/6265810">@Bob Bob</a> status CHANGED BEFORE -90d means "the issue has at least one status change older than 90 days". Negating it gives you issues with no change events older than 90 days. Brand-new issues match that, because all of their…

Hi @PLaksh11 , There's no native way to group or search Issue Type A by a field on its linked issues — JQL can't reach across links. The standard workaround is to mirror the field onto Issue Type A with Automation: Create the same "Risk Category Level" select field on Issue Type A (e.g. "Risk Category Level (from B)").…

Hi @bkneebone If I understand correctly, this is possible in Jira Cloud today. Each version's release page has a Related work section. Open the release (click the fix version on any work item, or go to your project's Releases page and select the version). In Related work, select Add related work, pick a category, and paste…

Hi @007989 The |0 default makes this worse, not better. When the lookup comes back empty, |0 turns the missing sum into a literal 0. The rule then writes that 0 to the parent. The empty lookup is the search index lagging behind the trigger, as @Gor Greyan said. You can't fully prevent that, but you can stop it from causing…

Hi @Sara Salem Adding to the automation suggestions above: if {{lookupIssues.Story Points.sum}} comes back empty, check which field your instance actually uses. Many instances have more than one story points field, and team-managed projects use a separate "Story point estimate" field. Referencing the field by ID avoids the…

Hi @Swapnil Two separate causes here: Story points showing empty — first verify customfield_11483 is actually the field holding the values: open https://<your-instance>/rest/api/2/issue/<SOME-KEY>?fields=customfield_11483 in a browser for an issue you know is pointed. If it returns null, you're referencing the wrong field…

Hi @jivan_patil JQL can't compare two fields to each other — the right-hand side of a clause has to be a literal value or a function, so resolutiondate > "Baseline End Date" treats the field name as text. That's a JQL limitation, not a syntax issue. The usual workaround is to have Automation record the result in a field…

Hi @Radhika Vijji Did you get a chance to try Plugio Suite for this? Would love to hear how it went, and whether anything was missing for your report.

Hi @An-Sofie Smet , This is a known quirk of the child issues panel: the column choice is saved, but the Σ aggregate values aren't re-fetched when the panel loads — removing/re-adding the column just forces a fresh fetch. There's no setting that fixes it. (Also note Σ Original Estimate only sums a task plus its own…

Hi @Kristina Svobodina , Unfortunately what you're hitting is a hard Jira limitation: subtasks can't be assigned to a sprint independently — they always follow their parent. There's no setting or workaround at the subtask level, so the fix has to be structural. Two realistic options: Option 1 — shift the whole hierarchy up…

Hi @rayyan_siddiqui This exact view — the tree with progress at every level — doesn't exist natively: saved filters always render flat lists and dashboards have no tree gadget. Plans (Premium) comes closest but lives outside filters and dashboards. Full disclosure — I'm the developer of Plugio Suite. Its Hierarchy widget…

Hi @Mahmoud Farouk +1 to the suggestion itself — "one gadget, multiple saved filters" has been coming up in the community for years, so it's definitely worth pushing through the in-product feedback channel as suggested above. In the meantime — full disclosure, I'm the developer of Plugio Suite — it takes a different route…

Hi @Deepali Dabholkar , You don't actually need story points for either of these — both work fine with issue counts. Sprint: Planned vs Closed stories. Set your board's estimation statistic to Issue count (Board settings → Estimation). The Velocity Chart on the board then shows Commitment vs Completed per sprint as plain…