Gor Greyan Expert

Dear @Andrzej Paszek Sorry, I wrongly understood your question :) In this case, I think you can do that without automation. Just no need to estimate the parent ticket, check the "Include subtaks" checkbox, which will calculate the sum of the sub-tasks' original estimate and time spent. If you are also estimating the…

Hi @Andrzej Paszek Welcome to the Atlassian Community! Here is the working version, tested on my side. Trigger: Work Logged Created Condition: Issuetype = Sub-Task Create Variable: wlStarted - {{worklog.started}} Create Variable: wlSecs - {{worklog.timeSpent}} Branch: For Parent Add Log Work: Time Spent - {{wlSecs}} Date…

Hi @gustave risbergs Welcome to the Atlassian Community! In the free plan, JSM allows up to 3 users. I think the issue is that you have 4 users. Try to remove one agent-user and see what the result is. https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/

Hi @Mahanth Prudhvi P I found this post in Community when our colleague shared this site to follow up on the changes. https://community.atlassian.com/forums/Jira-questions/Where-can-I-see-JIRA-Release-notes/qaq-p/3094637 https://cloud-updates.released.so/2025-10-20 Also, this Cloud Changes page may help you.…

Hi @admin Welcome to the Atlassian Community! Am I right that you want to have an End Date, which will be set now + Original Estimate? If yes, you can use this one; it should work {{now.plusBusinessDays(issue.timetracking.OriginalEstimateSeconds.divide(28800).round)}}

Dear @naresh Try clear browser cache and check if any extension is turned-on or not? If yed, turn off all extensions, and try again, it can be from the extension. Also, in chrome settings, allow third party cookies for your jira site. It is not connected with the jira or permission, the restriction come from the browser.

Hi @naresh Welcome to the Atlassian Community! There is no specific permission for the Attachment Downloading, if you can see the ticket, it is enough. Please confirm the following points. Have you tried clearing your browser cache? Do you see any error message, warning when you click “Download”? Do you have any browser…

Hi @Angelie Stephens Thank you for this great Idea, it was a good one. Moreover, for the beginners who are new here, in Jira and Confluence. I have successfully passed all 3 series :)

Hi @Angelie Stephens Thanks for this idea. I have passed the course — super helpful! Great course for beginners to understand the basic concept of Confluence. I have recommended it in our organization.

Hi @Angelie Stephens Thanks for this idea. I have passed the "Get started quickly with Jira" course, when I we have started to use Jira Cloud — super helpful! Great course for beginners to understand the basic concept of Jira. I have recommended it in our organization.

Hi @Michael Kobert Yes, my suggestion is to check the user's group or role with the User Condition. I couldn’t locate a public, dedicated request titled along the lines of "if user has access/permission to this issue”. If you’d like, you can open a new feature request so others can vote/watch. I could only find this one.…

Dear @Wyman Yan Admin section appears like this. One thing to check is the status properties. In the workflow, click on the status in which the ticket is, and you can not edit it, and check the properties.

Hi @Moser_ Elina What do you mean Category field? Is it customfield, which is available in the ticket, but you can not edit it?

Hi @David gonzalez It is Jira's question section. Please post the question in this link. https://community.atlassian.com/forums/Confluence/ct-p/confluence

Hi @AdnanFakhar Training Material Maybe this will help? I didn't do with scoped api. https://developer.atlassian.com/cloud/jira/platform/oauth-2-3lo-apps/

Dear @Wyman Yan Let's check it through the ticket, which you can't assign. Open the ticket, and you should see the "Admin" dropdown. After opening it, click on "Permission Helper". Write your username and select Assign Issue permission. Please provide a screenshot of the result.

Dear @Wyman Yan Could you also check the Service Desk Agent permission, as I can see it is a JSM project.

Hi, Dear @Biswash Lamsal I don't have any other better solution for now, as we are using native logging and Tempo for the planning.

Hi @Felipe de Almeida Toigo Yes, I also consider it a bug, as in our mathematical class we learn that <= is less than or equal :D So the date, which is equal to the date we wrote, should be included. Hope, one day it will be fixed.

Hi @Wyman Yan Could you also please share a screen from the permission section? There should be visible the "Assign Issue" permission and the roles/groups assigned to it. Also, please inform, what type of project it is?

Hi @Felipe de Almeida Toigo Yes, on my side, it is also working like that. There is no difference; using < or <=, it returns the same result. So, if I needed to include also 21, I put it like this <= 2025-10-22. I found this, which is reported on 12/Aug/2014 3:27 PM. https://jira.atlassian.com/browse/JRACLOUD-39509

Dear @Jared Schmitt If match() also didn't work, it can be because it wasn't applied to a string. Try this one, please. {{if( gt( webResponse.body.asJsonString.match("(customfield_(?:1|2))").size, 0 ), "fieldsPresent", "fieldsNotPresent" )}}

Dear @Biswash Lamsal Sorry, for the auto-adjustment, it is needed to use Jira's native log work dialog. I saw, Tempo doesn't have that feature.

Dear @Biswash Lamsal Sorry, one question. Your team is using Tempo for logging, am I right?

Hi @Jared Schmitt Yes, the "contains" is not supported. Instead, you can try to use match() {{if(or(webResponse.body.id.match("customfield_1"),webResponse.body.id.match("customfield_2")),"fieldsPresent","fieldsNotPresent")}} Please try the above-mentioned one.

Hi @Richard A_ Michaels Thanks for the question! In the workflow, on the create transition, add a validator type of "Regular Expression Check" validator and try this reg-ex for the field Summary. ^[^|]+\|[^|]+\|[^|]+$

Hi @Mihai Vasile Welcome to the Atlassian Community! There you don't need branch. Try this one. Trigger: Scheduled --> JQL - project = PROJECT AND duedate IS EMPTY Action: Send e-mail To: Reporter Subject: --- Body: -- Please let me know.

Dear @HQRAZAHS Get it, so I think, in this situation, the best practical setup remains:Initiative → Epic → Feature/Story/Task/Bug → Subtask

Hi @Staffan Bergh Welcome to the Atlassian Community! When you add multiple fields to the “Field value changed” trigger, the logic is OR — the rule will fire if any one of the selected fields changes. It won’t wait for all of them to change at once. If you need to access every field that changed, use the {{changelog}}…

Dear @HQRAZAHS Let me know if you need further assistance.