Comments
-
Hello @vaughan.dickson Yes this is possible. In the Edit Issue action add the Affected Versions field. Then select the COPY option. Then click in the text displayed in the field. This will give you a pop-up that lets you select the issue you want to copy from (Epic Issue) and the field you want to copy from (Fix Versions).
-
We didn't address your question about updating existing Epics, without making changes to the child stories. For that I would recommend that you create a Schedule trigger. In the Trigger include a JQL for selecting the Epic issues. Then add the Lookup Issues step and Edit Issues steps. You don't need any branches because…
-
Are you working with issues in a Team Managed project or a Company Managed project? That information will show at the bottom of the panel on the left when you are viewing the project. If you look at issue CST-392 does it show the Epic name/summary displayed in a field labeled "Epic Link" or "Parent" or "Parent Link"? Or do…
-
After selecting the Projects, Statuses, and Issue Types criteria, you can select the Story Points field by clicking on the +More button. Alternately you can switch to the JQL entry view for searching and type in the JQL statement directly. The Switch to JQL option shows to the right of the Search button. Here is an example…
-
There are multiple third party applications available that can report the time an issue spends in Statuses. Here is a link to search results from the Atlassian Marketplace. https://marketplace.atlassian.com/search?hosting=cloud&product=jira&query=time%20in%20status
-
You're welcome! If your questions have been satisfactorily addressed please consider marking the Answer as Accepted.
-
Use a Manual trigger and use the option to prompt the user for input. https://community.atlassian.com/t5/Automation-articles/Request-input-from-users-when-a-Manual-rule-is-triggered/ba-p/2333587
-
Have my answers helped you determine and confirm the root cause of your inability to edit the sprints? Can you share with us what you found the root cause to be?
-
Hello @Zach Taylor Welcome to the Atlassian community. In the Card Layout screen you should be able to add up to 3 fields to display on the cards in the Board view and 3 fields to display on the cards in the Backlog view. The field you need to add is the Status field. If you are not finding that, please provide a screen…
-
I misspoke about the fields being used; they are Start date and Due date, not End date. There is a Configure option that displays below the More Fields panel. Are you able to click on that to see if the Start and Due date fields are part of the issue layout? If not, you will need to add the fields to the screen(s) used by…
-
Hello @Hiti Verma Jira does not have a native gadget that tells you how many checkboxes in a checkbox field have been checked. You could possibly figure that out with an Automation Rule, store that value in another field, and then display that other field's value in a dashboard gadget.
-
Hello @Caroline Hazna Imelda Welcome to the Atlassian community. It sounds like what you want to set the card color based on comparing the Resolved Date to the Create Date. Is that correct? Jira does not natively support comparing two date fields to each other in a JQL, which is how card colors may be set in a board. It…
-
Hello @Leandro Santos Is the user's email stored somewhere in the issue? If so, the Send Email action in an Automation rule can be used to send an email to that address. However the From address on the email cannot be customized - it will appear as "automation@<your Jira URL>" There is no option to customize the outgoing…
-
Hello @Hartej.Gill Welcome to the Atlassian community. Based on this documentation there is no "endOfDay" function that can be used to set the time portion of a date/time field. If you are looking for a function that set the time based on the end of your business hours vs. the end of the actual day, there are no functions…
-
Hello @CC You will need a separate rule to catch when an issue is removed from an Epic. This rule includes Log actions with the Smart Values that give you the New and Original value for the Epic Link when it has been changed. What you care about is when the {{fromString}} value is not EMPTY. That means the issue was…
-
Hello @Juan Manuel Ramos Taboada Can you match what is shown in the first image to an actual Epic? How about what is shown in the second image? If you can match both to actual Epics, are they in fact two different Epics? If you look at the history for the issue does it show the Epic Link field being changed from one value…
-
Hello @DeMeritt_ Matthew Welcome to the Atlassian community. Another place to look for the version number for the non-Cloud product is at the bottom of most screens (the login screen, the bottom of the home screen, the bottom of dashboard screens). In addition to determining if you are using the Cloud product or a…
-
Essentially, yes. That has been my experience with both self-hosted and Cloud Jira Software. I always have made a point of educating the users of Jira systems I admin'd to create sprint names that reflect their board name, or team name, or product name - something that readily gives an idea of the "ownership" of the…
-
A workflow defines the Statuses through which an issue can transition, and rules/actions associated with those transitions. A workflow scheme associates workflows to issue types. A Workflow Scheme will always have a Default workflow specified. That is the Workflow that will be used for any issue type that has not been…
-
Hi DeAnne, I have not worked much with Forms in Jira Service Management, so I am only about 95% sure you can't include with the form any sort of check against pre-existing issues to see if there is one that already includes the email value. I think with native functionality your only path forward is to detect that after…
-
The Screen Scheme enables you to have different screens for the Create Issue operation and the Edit Issue operation. Default specifies the screen to use if either Create Issue or Edit Issue operations are not explicitly defined. If all three are using the same screen, then you could delete the entries for the Create Issue…
-
Hello @Rauser Welcome to the Atlassian community. Are you working with a Roadmap for a Scrum board or a Kanban board? Are you working with a Team Managed project or a Company Managed project? That information will show at the bottom of the navigation panel on the left. Generally the bars are based on the Start date and End…
-
Hello @Phil Bustin As you found in your sandbox it is possible to build new workflows without impacting existing workflows and issues. Is there a step by step guide for this? I don't think there is. The basic concept is to create new items and not make changes to any pre-existing items. For workflows you create new…
-
Hello @Cash Coyne With a Schedule trigger the actions within the rule will be run once for each issue returned in the JQL associated with the trigger. What is the CurDev variable being set to? What is its purpose? Why do you have a JQL in the trigger and then use a Lookup Issues action to run the same JQL with an…
-
Hello @Sam Given that you see a version number for Jira at the bottom of your screens, that indicates you are not using the Jira Cloud product. You are using a self-hosted Jira product (Jira Server or Jira Data Center). In that case you are using the project architecture referred to in Jira Cloud as "Company Managed" and…
-
Hello @Donna Macauley My experience has been that the expiration is based on Atlassian HQ timezone (Sydney). Additionally, make sure you are looking at the dates shown in my.atlassian.com rather than the dates shown within the Jira and Confluence applications. Several years ago when I was part of the admin team for…
-
Hello @CC Since your questions are going beyond the bounds of the original post, which also already has an accepted answer, please start a new post for your additional questions. I recommend that you include a link to this post to show the material you referenced in your efforts. Also, please post a complete copy of your…
-
Hello @DeAnne Russ Have you set up your issue types and custom fields? How are the issues created? Are your PMs creating the issues directly in Jira or sending emails to have the issue created? Are you using the Jira Software, Jira Work Management, or Jira Service Management product for tracking these requests? Natively it…
-
Hello @Jeff Hooper What does the rule Audit Log show you for the execution of the rule? In what way is the rule not working? Is this for issues in a Team Managed project or a Company Managed project? I think the problem might be in your Branch step. I think it needs to be For: Epic (parent)
-
こんにちは、 それが Days In Column 機能です。カスタマイズはできません。この機能に関する情報は、次の場所で見つけることができます。 https://support.atlassian.com/jira-software-cloud/docs/customize-cards/#Using-Days-in-column 情報はアクセスできるフィールドには保存されません。 問題が特定のステータスに費やした日数を追跡したい場合は、自動化ルールを開発するか、サードパーティのアプリケーションを使用することで実行できます。 --- Hello, That is the Days In Column feature. It is not…