Comments
-
@Marc -Devoteam- Probably he referencing to that https://jira.atlassian.com/browse/JRACLOUD-67916 And problems with referencing Subquery, but that doesn't changing a point, either he try multiple JQL Query, combine them ”Dirty way" or grab Addon. The thing is we giving advices but User gived more his Pain out about that,…
-
@Chaouky.ElKantaoui.ext Hello. I checked the current Atlassian docs/pricing because this changed recently. In Cloud, Assets is best described as a Jira Service Management capability (not a separate standalone app you buy on its own). What’s true today: Assets is part of the Jira Service Management / Service Collection…
-
Hello @Eric Guesdon I get the frustration, but this one is actually simpler than it looks, and it’s not “AI tax”. In Jira Cloud you can pull parent + subtasks in one filter. You just need to search by issue type + use the parent relationship. Try this: All parents (your work type): project = XYZ AND issuetype = "BZF…
-
Hello @jakob Furtner you’re not missing anything. This isn’t a Confluence setting issue, it’s an Atlassian billing eligibility restriction. Your screenshot clearly says: “Pay later by invoice (within 14 days) not available for this order.” That means your organization is currently not eligible for invoice / payment terms…
-
Thank you so much @Jimmy Seddon for all you've done.
-
Hello and Welcome @Jay Sharma A workflow update by itself doesn’t normally wipe Sprint values. Changing statuses can move issues around, but it shouldn’t turn Sprint into “None”. So something else likely changed at the same time. Here’s where I’d look first: 1) Board filter / board scope changed Sprint reporting is tied to…
-
@Tejaswini S And did Atlassian provided a Reason for it ?
-
Hello @Tejaswini S When thats occur more Often, if i will be in your Place, i would reach out to Support.
-
@Oleksii Melnyk _MOY Apps_ Love this write-up, you nailed the real problem: Assets is usually “perfectly tracked” and still invisible to the people it’s about, which then creates tickets for information you already have. If I had to answer your “which approach is best” question: For me, Option 2 (self-service in the…
-
Hello @Sherry Nightingale Love that you’re doing this properly instead of just “winging the exam” 🙂 Since you already have 8 years of Jira experience and 2.5 as an admin, you’re not starting from zero. So I’d structure this strategically, not generically. If you’re focused on Jira Cloud, the natural progression usually…
-
Hello @melanie test Free Jira Cloud doesn’t have a fixed expiration date, but it can be deactivated if nobody uses it for a long time. What likely happened to you: If your site was mainly used for testing and then sat idle, Atlassian can deactivate Free-only sites after a long inactivity period (commonly cited as around…
-
Hello @khawla No Atlassian won’t delete the fields for you just because the new “unused field optimization” says they’re unused. What this feature is really about is reducing field bloat in configuration, not silently destroying your data. What happens if you do nothing: Atlassian may recommend fields to clean up. But the…
-
@Jim P Yep that screenshot is exactly the problem. Right now you have: Create Story Create Sub-task …but both actions are still running in the Feature context, because you never switched the “current issue” to the Story. So Jira happily creates the sub-task under the Feature. What to change You need a Branch between those…
-
Ctrl + Shift + i - Labels
-
Hello @Jim P You’re close, the problem is rule context. Create sub-tasks always creates them under the current issue. Since your rule is triggered on the Feature, Jira treats the Feature as the current issue, so the sub-tasks get added there. What you need to do is: Trigger: Feature transitions from Discovery → Started…
-
Hello @Roger Bradley in Jira Cloud, there’s no native dashboard gadget that will do that percentage calculation for you. You can get the two counts easily, but Jira won’t do the “Empty / Total = %” math in a gadget. What works without apps: Create 2 saved filters per timeframe: Total (timeframe A) = your JQL Empty…
-
Hello @Prakash Singh Chauhan Labels/tags are still there in Confluence Cloud, they’re just a bit hidden depending on the page header layout. Do this: Open the page -> top right … (More actions) -> Add labels (sometimes it just shows as Labels) -> type your keywords -> add them. And yep: once you start using labels…
-
@Vallala Ujwala You already get answer in your old Question Post. Please not multiple them as we already acknowledge you, there's no way to Scope that granulary only to specific role, as that's basic Admin function.
-
Hello @Rahul Borade Jira Cloud JSM doesn’t do “repeatable rows / add another line item” natively on portal forms. The form/table bits are basically static, so you end up with the ugly “Expense 1 / 2 / 3” pattern if you stay out-of-the-box. If you want real line items (Type / Date / Amount / Description with an “add row”…
-
Hello @Omkar Rajale first thing: this is almost always project type related, not some mysterious “field upgrade” from Atlassian 🙂 So split it like this: If it’s company-managed: Even if the field is on the correct Screen and not hidden in Field Configuration, the Issue Layout can still hide it in the new issue view. So go…
-
Hello @Steven Barks That “last billing admin” message is the giveaway: something under your email is still active somewhere (org/site/subscription state), even if you deleted stuff back in 2022. The emails are likely coming from that. What I’d do: Log in and check admin.atlassian.com → see if any org/site still exists…
-
@Mateusz Janus Glad it worked. Don’t exaggerate 🤣 If you think about it, it’s actually quite logical. If the user account you’re using doesn’t have the proper permissions to perform that action, then the automation won’t have that option either. That’s how layered permission schemes work, which is why automations should…
-
@Vallala Ujwala here Cloud is very different than DC. In Jira Cloud you can’t do the old Data Center trick with ScriptRunner fragments (injecting JS/HTML, targeting IDs/classes, making fields read-only on the fly). Cloud simply doesn’t allow that kind of UI manipulation.
-
@Mateusz Janus Either your Automation Component is outdated or your user don't have sufficient permission in this Project for delete own and others attachments.
-
@Mateusz Janus Which DC Version you have?
-
@Mateusz Janus @Florian Bonniec Biggest problem here that without ScriptRunner you can't put here intelligent delta logic and with Automation in this case only more less rebuild Logic. Limitation are in Copy Logic Not Trigger Logic. Automation in DC: Can copy attachments Cannot compare attachment lists Cannot identify…
-
Cześć @Mateusz Janus 🙂 Yep for mirror mode that’s exactly what I mean, and it is kind of a clever hack in Cloud/DC terms: Branch to Ticket B → remove attachments on B → then copy attachments from Ticket A. Result: no duplicates, always clean. Only downside: Ticket B must be a “follower” anything attached directly to B will…
-
Hello and good Sunday @Vallala Ujwala Yep but sadly not in the way you want. In JSM company-managed, Channel access is part of project configuration. So if someone is a Project Admin on that project, they can change it. Cloud doesn’t give you a separate permission like “can admin the project, but can’t touch…