Sanjog Sigdel Community Champion

Hi @Shilpa Shetty Welcome to the community. Please check Jira Software Permission Schemes. This will give you answer to manage project and activity to specific user or a group of user. For reference go through the thread of this post for some information on Permission scheme:-…

Hello @Andrew Moisov , Welcome to the community. Error 500 is service/firewall issues label. You must be facing some service unreachable or unauthorized issue in your Jira server. If this is happening frequently, please contact your administrator

Hello @David Verbeure Welcome to the community. I came to find following information about completed work and initial completed work(Assumption) Completed Work: refers to the sum of the story points, story counts, or work items that have been marked completed during the sprint. It represents the actual work that the team…

Hello @Marek Bugar Welcome to the community. Please contact your Jira Administrator and check if there has been some admin config changes. Or else create a ticket at support.atlassian.com for assistance from Atlassian Support Team.

Hello @satishkumar Welcome to the group. If you have admin access in your Jira Application, you can find Audit Logs under the Systems Setting Hope this helps you

Hey @subash_duraipandi, Please go through this answer. I have shared the details on how to add total story points, copleted and remaining in an EPIC using Jira Automation, Smart Valus and Lookup Issues.…

Hello @AlaaKassemSenousy , Welcome to the community. If you create a ticket and three sub tasks for ios, Android and Backend it should solve your problem. Each developer will log their hours in their respective sub-tasks. The main ticket can be assigned to anyone. In the main ticket total hours logged in three sub-tasks…

Hello @subash_duraipandi The default Jira dashboard donot have such gadgets to display How many stories point, hours , Stories and Bugs are done by Specific user. JIRA Automation, Lookup Issues and Smart Values However there is a workaround. * Create Custom fields for your specific requirements. * For example create Total…

Hello @Lena Boiser Welcome to the community! So far to my knowledge the percentage comparision, counting the issues, summing the values etc. via JQL. I've so far seen the less than <, greater than > comparision for the days and dates in the JQL. Using Jira Smart Values we can perform sum and other operations. I'm sure…

Welcome to the community @Prasad Kalamkar 

Welcome to the community @Chu Dam 

Hi @Santhana Raj Maharajan Can you please elaborate what you mean by separating out the closed issues? And where do you want to display those separated closed issues? In order to separate the issues with status CLOSED, you can have a quick filter in your board. * Go to Board setting * Go to quick filter * Add Name: Closed…

Hi @Kseniia Trushnikova I have also tried the same automation rule to close the Epic when all children issues are completed.

Hello @Will Schultz Welcome to the community What does the Statuses for Task, Epic and Subtask Manage workflow under the To Do column mean? Did you try creating all kinds of issues like Story, Bugs, Task and none appeared in the board? What is the default status in your workflow when you first create the ticket? Your issue…

Hi @Matthew Van Doremalen Like @David Blank I have implemented somethign with Jira Automation rule. WHenever a new USer Story is created, the Automation rule creates a sub task called Documentation-Sub task, assigns it to the BA guy, a Design subtask and assigns it to the UI/UX designer.

Hello @Steve Diaz Welcome to the community. I'll share points on how you can achieve your requirements: * Create separate workflows under a workflow scheme.* Map issue types as per th workflows. * Bug - Bug workflow with relevant statuses * Story, Task workflow * Spike workflow * EPIC workflow * Try to be generic such that…

Hi @AlaaKassemSenousy If you have properly set as the Filed Original Estimate is required in your validator in the Post function it should work. Meanwhile check if other time tracking related fileds are available in the fields or not. We need to add the validator mentioning a filed "Original Estimate" as required.

Hello Community. It's been a while and I am enjoying the interaction with the awesome community contributors, leaders and managers. 

Hello @Carole DeRoche Welcome to the community. You are already there. Questions, comments, articles and discussions are the mains of the community. Ask precise questions with illustrated details such that the community can contribute in answering your curiosity. And go to the Atlassian university to learn skills of your…

Hello @Carole DeRoche Welcome to the community. You are already there. Questions, comments, articles and discussions are the mains of the community. Ask precise questions with illustrated details such that the community can contribute in answering your curiosity. And go to the Atlassian university to learn skills of your…

Hey @Ondřej Rolník I am running Jira Standard Plan so my Automation rule limit is 500. But if you have premium Jira Plan, you can run as many automatio nrule as you want. In that case the trigger can be whenever the Story Point value gets changes. Better than the issue is updated, keep it as whenever the story points value…

Hey @Ondřej Rolník It should be like "Epic Link" = {{issue.key}} and Status = Done AND Status in (Done, "Won't Do") For a good practice to eliminate errors, better if you replace Won't Do to Wont Do. Just to be in safe side such that the single quote ' won't create any issue. Please validate your JQL first from the Jira…

@Ondřej Rolník I have {{lookupIssues.Story Points.sum}} for all three fields. The jql in each lookup issues separates tickets with completed, remaining and total story points. This smart value sums the story points. This is how it works for me.

Hello @Gemma Welcome to the community. Please submit a support request at support.atlassian.com to bring your issue to attention.

Hello @Ondřej Rolník The rest of the automation is extended on the same flow. Three lookup issues with minor changes gives os total points, completed and remaining in a single automation. Please see the automation below which covers all three points I've mentioned in the answer above:

Hey @Nic Brough -Adaptavist- I learnt something new today. I was looking for changing the resolution for some time and finally found it. Thanks for sharing this answer.

Hey @emilio.ortega.m This solution is easy. Put all of the status that you consider as the final states at the end column(The last column of your Project Board). You can do this from Column Management in Project Setting. For me tickets with Done, Closed, Ready for Prod and Approved statuses are the final status. If any…

JQL Search recommendations should display your status while you type Review. Simply put multiple statuses like this: linkedIssuesOf(summary, "Review Draft", Done) 

Hi Rajat, Somewhere below the JQL fetching action these should be a checkbox. It indicates whether to fetch the entire results again or fetch only the latest results from last execution. Is that the missing part? Your Automation rule looks fine from what you have mentioned 

Hi @Aveetha Singh * Check for the Validation and Condition under the Workflow Transition. By default when you create a ticket it can be in Backlog or ToDo status. Maybe there is a post function in the Workflow in that status. * To see the fields, in your issue creation screen, in top right section, configuration field…