Gor Greyan Expert

Dear @Marc -Devoteam- Thanks a lot, my friend.

Hi @Marc -Devoteam- Thanks for the answer. I have Scriptrunner, but couldn't find any appropriate JQL. Do you know any?

Hi @Illia Drachuk Thanks for the question. When you update ranking via the Agile API rest/agile/1.0/issue/rank, the change is applied immediately for Agile views. However, JQL search relies on Jira’s search index, which is eventually consistent in Cloud. That is why there can be a short delay before the updated ranking is…

Hi @Whitney Stambler Welcome to the Atlassian Community! 1. Chart alignment on the dashboard In Jira Gadgets don’t have fixed heights, they expand based on their content (legends, filters, titles), and Jira doesn’t give you control over spacing or precise alignment between columns. As a solution, you can keep both charts…

Hi @Marc -Devoteam- Thanks for the clarification.

Hi @Kumkum Geervani Welcome to the Atlassian Community! The / _edge / tenant_info endpoint is not part of Atlassian’s supported API, so it shouldn’t be relied on, even if it currently returns the cloudId. The supported way to retrieve the cloudId is via the official OAuth endpoint:GET…

Hi @Carolina SILVA Thanks for the clarification. In that case, this isn’t coming from Jira itself, but from your data loading process. Jira does not automatically copy versions into new projects, so if all versions (including released ones) appear, they are being created or synced during your data load ( via API, script).…

Hi @Mathias Jacob Welcome to the Atlassian Community! Jira Cloud doesn’t use a single fixed IP address for outbound connections; it uses a range of IPs depending on the region and service. That’s why even if you’ve whitelisted one IP in GitHub, the connection can still be blocked. To resolve this, you need to allow…

Hi @Ömer Gündüz Welcome to the Atlassian Community! In Jira Service Management, holidays in SLA calendars are supported as full-day only, and there’s no native option to define partial or half-day holidays. As a workaround, you would need to adjust working hours or use custom solutions(search for 3-rd party apps), since…

Hi @Carolina SILVA Thanks for the question. I think this happens because versions are linked to issues. When you create a new project, Jira brings over all versions that are associated with those issues — even old/released ones. So if your issues were linked to historical versions, those versions will appear in the new…

Hi @Rob Hean, This is amazing 🙂 I’ve already watched your ACP-620 course, and I can honestly say it’s been very helpful for my exam preparation.

Hi @Tefik Iseinovic You should focus on the main board filter, not the Quick Filters. Quick Filters only affect what you see temporarily, while the board filter defines which issues — and therefore which sprints — belong to the board. You can check this in Board settings → General → Filter query to see which filter the…

Dear @chisato3_egashira Yes, do you want me to share an automation example,how to set that?

Hi @Lindie Meyer Welcome to the Atlassian Community! Am I right that the part visible in the screenshot is not available for you?

Hi @chisato3_egashira Welcome to the Atlassian Community! Jira doesn’t provide native functionality to copy priority changes across hierarchical levels automatically, parent → child → sub-task. Each issue’s priority is managed independently. To achieve this kind of behavior, you would need to use Automation rules (for…

@Sherif Mansour Thanks for the great content. Will there be any new updates in 2026?

Hi @Tefik Iseinovic Welcome to the Atlassian Community! This can happen when both boards are sharing the same filter scope, so when a sprint is started or completed on one board, it affects the other. In Jira, a sprint belongs to a single board/filter, not to individual teams. Most likely, your FE and BE boards have…

Hi @Ole Rosendal Welcome to the Atlassian Community! In general, marketplace apps like ScriptRunner or eazyBI respect Jira’s permission model, so they can only access data that the user is allowed to see. The correct way to control access is via project permissions, issue security, and group membership — if user X can only…

Hi @Arkadiusz Wroblewski Voted for that, thank you very much for raising that.

Dear @Hannah If the solution worked for you, kindly ask you to accept the answer.

Hi @Hannah Welcome to the Atlassian Community! The Two-Dimensional Filter Statistics gadget should reflect the saved filter exactly as defined. If it looks like it’s pulling issues from other projects, the first thing to check is the filter itself. I noticed, that you mention that it works correctly when running…

Hi @Hannah Welcome to the Atlassian Community! It can happen because the issue is updated multiple times, triggering the rule multiple times. I’d recommend adding a condition using {{changelog.status.from}} / {{changelog.status.to}} to ensure the rule only runs for the specific transition. If you can share your rule…

Hi @Md Mostofa Maruf Welcome to the Atlassian Community! The “overdue” indicator in Jira is based purely on the Due date vs current date, and it doesn’t automatically consider the issue status (Done or Not Required). If you want to remove the overdue flag for completed issues while keeping the due date, a common workaround…

Hi @WangJie Welcome to the Atlassian Community! Have you tried on a different browser, in incognito mode, and/or on a different device?

Hi @nagata shumpei Welcome to the Atlassian Community! In Jira Cloud, users in “invited” status can still receive notifications as long as they are added to projects/groups and have a valid email address, even if they haven’t completed account activation yet. In contrast, deactivated users do not receive notifications, as…

Dear @Jonathan Porta For resetting the value, you can do something like: def field = getFieldById("customfield_xxxxx") def originalValue = field.getValue() field.setFormValue(originalValue) Yes, I think you can raise this with Adaptavist; it is likely a bug in how Cloud Behaviours interact with the new issue view.

Hi @Jonathan Porta Thanks for the question. As a workaround, I suggest that, instead of making the field read-only, you can keep it visible using setHidden(false) and control behavior via validation (e.g., prevent changes or reset the value if modified). def field = getFieldById("customfield_xxxxx") field.setHidden(false)

Dear @Peter_DevSamurai Thanks for the feedback and Kudos :) Glad that it helps. Have a great weekend!

Dear @Asier Vadillo Yes, via the Validator, this isn’t possible with native Jira Cloud functionality. Built-in validators can check if a field is empty or required, but they don’t support validating against a specific user. For your use case, the only way to enforce this is via Automation (send back to the previous status)…

@Jonnie Bloor You are welcome. Have a good day!