Trudy P Claspill Community Champion

Hello @Carlos Alvarado Welcome to the Atlassian community. Based on the image you provide you appear to be working with a Team Managed project. You can confirm that by looking at the message displayed at the bottom of the panel on the left. The functionality you describe is not available in the Scrum Backlog screen for…

Can you clarify what issues the contractor needs to access in separate sentences? 1. The contractor needs access to issue in Project A that are created by a specific account. 2. The contractor needs access to issues in "any other Jira project"... It is the second item for which we need a more complete statement about the…

Hello @Tomasz Swiniarski Jira does not automatically roll up time spent from child issues to Epics. If you want that done you would need to create an Automation Rule to do it. The native aggregate field for Time Spent does not appear to be a field that can be directly editing in an issue through Automation. It seems the…

Hello @venkatesh bojja Jira doesn't allow issues to be added to Sprints that are closed. You would need to reopen the closed sprints to add the issues to them and then re-close them, and that would change the end date for the sprints. I am curious about the steps you executed when you say you "migrated the workflow". I…

I see the same behavior. I see this issue fixed 2 days ago that the field didn't previously display at all on the Create screen. Maybe adding the field label was missed in the fix. https://jira.atlassian.com/browse/JRACLOUD-81077 I recommend you have you Jira Administrators raise the issue with Atlassian support so a bug…

Hello @Vitalii Kostyrka Welcome to the Atlassian community. Are you working with a Company Managed project or a Team Managed project? That information will show at the bottom of the panel on the left. Can you show us a screen image of what you see? If you type in the name of a missing sprint does the list show you a match?

Hello @Akshay Tanpure Welcome to the Atlassian community. Jira does not natively support creating JQL that will compare one issue date field to another issue date field. You could use Automation for Jira to do that comparison and set a custom field in the issue to note if the issue was closed in less than or more than one…

Clever work around, @Walter Buggenhout ,though it does wipe out all the other issue history and comments, and could require recreating link relationships if the original had those also.

Hello @Christopher Gordon Welcome to the Atlassian community. You will have to use the Advanced Field Editing with JSON feature. You can use either an explicit value or a smart value for the name of the Version you want to add. { "update": { "fixVersions" : [ { "add": { "name":"CRS 2.0" } } ] } }

I remember a few specific things from my first year of school, but I don't know which one was the earliest. * when we were learning the alphabet and the teacher would point to the letters posted on the wall and call on a student to name the letter. * the Christmas gift I got and who it was from for the gift exchange. * at…

@Jose Suarez As I recommended to the original poster, I recommend you have your Jira Administrators open a support case with Atlassian Support to investigate the issue.

That would require a method for changing or deleting change history for the issue and/or sprint, and I'm 90% sure there is no supported UI or API method for doing that in Cloud. And since we don't have direct access to the database in Cloud, you can't use a database hack to correct it. Since you are on a paid plan you…

こんにちは @hiroyuki kadowaki 、 コミュニティへようこそ。 [期間] フィールドを [カスタム] に変更します。次に、必要な期間に一致する開始日と終了日を追加できます。 -- Hello, Welcome to the community. Change the Duration field to Custom. Then you can add a start and end date to match the duration you want. Is it possible to set the duration of sprints as 3 months, 6 months, 1 year, 2 years?…

In the Audit Log you can expand an entry to show the details of the execution. What are those details? The log entry will show Success as long as there was not a catastrophic error. It won't show an error if you have used an incorrect smart value to try to set a field. Given that, I suggest that you add a Log action to…

Caveat - I am not deeply familiar with Advanced Roadmaps, so there may be cross project/plan sprint features of which I am unaware. Jira does not restrict which issues can be added to a sprint. By editing the Sprint field directly you can specify any sprint from any board that you have permission to see. However... If you…

Hello @Victoria Kramarenko Your requirement cannot be met with native Jira functionality. Would you consider adding a third party application to your Jira system?

Hello @Nada Alahmadi Welcome to the Atlassian community. Can you show us the complete rule that creates the second request? Can you show us an example of the details of a second request issue that has been created by the automation? Where and when are you getting the message "Everyone from 'Budget Approver' must approve"?

Hello @Dmitrii Ludin Welcome to the Atlassian community. Does the user get an acknowledgement email that their issue was created? How are you answering the user through the task? Are you adding a comment? If so are you using the Reply To Customer option? Have you checked the Customer Notification settings for the project…

Hello @Swaroop Kumar In what type of step in the automation rule are you trying to select the field? Please provide a screen image of what you see.

Do you want the rule triggered by a change in the field in one of the linked or child issues, or is it triggered by a change in the field in the parent issue? What are the issue types of these issues (parent, linked, and children)? The default issue hierarchy in Jira is Epic level issues |-- base level issues |-- subtask…

Hello @Adam Rivera No, that is not possible. You can check to see if a change request exist for that, and open one if it does not, here: https://jira.atlassian.com/secure/Dashboard.jspa

Hello @Tushar Shinde Welcome to the Atlassian community! Please show us your entire rule and the Audit Log details that go with the execution of the rule. We cannot offer advice on how to change your rule without those details.

Hello @Mona Aghamirsalim You need to use a Lookup Issue action within in your For branch to lookup the child issues of the Epic. You'll have to change the field name from "Story Points" to the name you use for your field.

Hello @Scott Robertson While there may be only one Start date field showing in your project there could still be additional custom fields created with the same name. Your Jira Administrator can check the Custom Fields list to see if there are multiple fields with the same name. If there are, there are a couple of choices…

Hello @Riley Piper When an Epic is moved to a "done" status the Resolution field for the Epic should also be getting set. When the Resolution field is set, that causes the Resolved date/timestamp field to be set. You can use the Resolved field in filters to select issues by when they were resolved, and you can display the…

Hello @Kelly McAteer This rule works for #2 And this works for #1, though you will need to adjust the actual status values used.

Hello @Sanjog Sigdel To use the {{lookupIssues}} smart value you must first use the Lookup Issues action.

こんにちは @kyosuke takasaki 、 アトラシアン コミュニティへようこそ。 課題がボード上の最も右の列にある場合にのみ、スプリントで完了したとみなされます。それはあなたの問題にも当てはまりますか？ --- Hello @kyosuke takasaki , Welcome to the Atlassian community. An issue will be considered completed in a sprint only if it is in the column farthest to the right on the board. Is that true for your issues?

Hello @Santosh Welcome to the Atlassian community. I have alerted the Atlassian team members to your issue. They will reach out to you.

Hello @Chad Bellan Welcome to the Atlassian community. When you login to Jira, what is the URL that shows in the browser when you complete the login? Is it the same as the one you mentioned in your post? The Jira issue should be created in the Jira instance to which you are currently logged in. Make sure you are logged in…