Pasam Venkateshwarrao Expert

Hi @Dominik Trunk Thanks for reaching out, post-upgrade can you please check In Jira -->Go to System ---> Logging and profiling Configure the level and set the below packages to bug com.atlassian.jira.mail com.atlassian.mail.outgoing After that can create a test ticket and create a comment and check whether it is delivered…

@Zhenis Beisekov Thanks for sharing such a useful content i have tried the ACLI in my instance and worked with all commands But to create a project using ACLI is not working.

Hi @mariana Welcome to the community,Your question is how to access development information per ticket in JIRA right. Here is the Answer, If you open the Jira ticket under Apps (below the issue summary) you can see Git Development if you click on that you can see the Pull Request and Branches information,i have attached…

@butch as i said if it not works can you raise a support ticket to atlassian team https://support.atlassian.com/contact/

@Pendem, Anjaneyulu you are not able to edit summary,title after creating the ticket is that right. one way is please check whether there are any restriction in workflow properties like jira.permission.edit.denied and another way is check issue level security scheme permissions. Hope this helps

@butch yes for that can you please check in spam/promotions/junk folders in the Email can you please confirm subscriptions@<our company email> is Distribution list or full mail box

@Vineet Yes this can be possible through Automation Automation Example Trigger: Scheduled Select Every day or prefer time Select: “Run JQL search” Insert JQL: assignee IS NOT EMPTY AND updated <= -7d Condition - optional: You can add a "Status is not Done" condition to avoid closed issues. Action: Add Comment issue has not…

Hi @butch Thanks for reaching out to community,If you are using a work email, the company firewall or email filter may be blocking Atlassian emails ask your IT team to whitelist the domain contains @atlassian.com after that if it not works raise a request at https://support.atlassian.com/contact/ Hope this helps

@Marika Beyne in Advanced Roadmap plan you can see the correct data,I have tried and I came to know that “Goal” field is not supported in backlog/card layout view Jira backlog UI doesn’t fully support some special fields “Goal” is one of those fields that only shows up properly in Plans or issue detail view, but not…

@Piyush Annadate _ACE Pune_ Thanks for the information for sharing the guidelines

Hi @Bharath Avula Welcome to the community, First, check your Jira personal settings and see if you have the option "Send email notifications" when you are the watcher, reporter of the issue etc.If this is set up correctly, Atlassian has put the email to the suppression list. This is done in order to prevent spam. In this…

Hi @Marika Beyne Welcome to the community,Goals are typically linked via the "Goal" field in Advanced Roadmaps (Plans) — not visible in the backlog by default,Only works if you’ve linked Goals to issues using Advanced Roadmaps, can you confirm whether you are using Advanced Roadmaps or Timeline. Hope this helps

@AMIT GULATI if it works for you can hit accept answer so that it will help to others those who are facing the same issue

@AMIT GULATI Instead of 15 filters, use one base filter (e.g., all issues with team labels) and define quick filters inside Structure views. How: In Structure, go to Views → Manage Views Define a view with multiple Quick Filters like:labels = team1labels = team2labels in ("team1", "team2") // multi-team view Hope this helps

@AMIT GULATI Use "Filter by Attribute... (with Sub-Items)" Instead of a plain filter: Click the filter icon (funnel) in the Structure toolbar. Select “Add Filter → Attribute...” Choose: Label → contains → Team 1 (or your desired label) Important: Enable "Keep sub-items of matching items" This tells Structure:"Even if a…

@Michael Kaufmann This is the correct syntax if you're using ScriptRunner Cloud and want to get the total remaining estimate for a user, filtered by project and fixVersion: issueFunction in aggregateExpression( "Remaining Estimate", "remainingEstimate.sum('assignee = venkat AND project = ABC AND fixVersion in (V1, V1.1)')"…

@Michael Kaufmann can you try with the query which i have shared in the previous reply

@Michael Kaufmann If you're using a ScriptRunner function like aggregateExpression(), this is correct: issueFunction in aggregateExpression( "Remaining Estimate", "remainingEstimate.sum(filter = 'assignee = venkat AND project = ABC')")If you're still unsure, paste your full query 

Hi @Mertcan Yuksel In Jira Cloud, default labels (i.e., ones that auto-suggest or auto-complete when typing) are not stored separately — labels are just free text added to issues. Jira doesn't have a concept of “default” or pre-defined labels, so You cannot delete labels globally in the UI like custom fields or statuses.…

@Michael Kaufmann Script Runner expects only one argument BUT — you’re giving 3 arguments, which causes this error, use the below JQL issueFunction in aggregateExpression( "Remaining for venkat", "remainingEstimate.sum(filter = 'assignee = venkat AND project = abc AND fixVersion in (V1, V1.1)')" ) Note: the filter goes…

@Vera Ujlaki if this helps to you can you hit accept answer 

@Joicy Joy have you tried this or if this helped to you can you hit accept answer so that it will be helpful to other those who are looking for the same question

@Ivaylo Kostadinov is this helps to your query?

@Isabel Monsalve (Contractor) if this helps to you can you hit accept answer so that it will be useful to others those who are looking for the same question

@James Walters the steps which i have shared is it helps to you

@Neil Poska In Advanced Roadmaps(Premium Plan) you can do it Configure Advanced Roadmaps Go to: Plans → Plan Settings → Customize view→ Scroll to Custom fields→ Enable your custom estimate field→ Make sure it is aggregated (you'll see a "Σ" icon when it's being rolled up) This will now sum up values from child issues…

Hi @Neil Poska Welcome to the community,you can set automation like below Trigger: "Issue Created" (or any trigger you want) Action: “Edit issue” Click “Add action” Choose “Edit issue” chosse the field At the bottom, click “More options” Use Smart Values : { "fields": { "timetracking": { "originalEstimate":…

Hi @James Walters welcome to the community,if child issues are not showing then there will be one of the following Check Issue Type Hierarchy Jira needs to recognize the parent-child relationship (like Epic → Story → Sub-task). Go to:Jira Settings → Issues → Issue Type Hierarchy In the Issue View: Open a parent issue…

Hi @Michael Kaufmann using ScriptRunner's issueFunction in aggregateExpression(...) is the right direction, but to get estimated hours per assignee, you need a slightly different approach because aggregateExpression gives you a single value across all matching issues, not per assignee directly. issueFunction in…

Hi @joaovitorribeiro Welcome to the community,you can set this by using Automation Step:1 Save the Previous Status When Pausing Trigger: Field value changed → Field: Status Condition: New status = Paused (or whatever your pause status is) Action: Edit issue → Text field (e.g., Previous Status)…