Bill Sheboy Expert

Hi @Anna I have seen this symptom noted in a few other posts: issue linking does not occur at the time of issue create, and instead happens as a separate edit. This happens for manual issue creation and by automation rules. Which is curious as the REST API does support adding one link, but not several. And so that is…

Hi @Michael Wu -- Welcome to the Atlassian Community! That seems to be a known issue for the Cloud and Server versions of automation. You may vote for / watch this item (and the linked ones) here: https://jira.atlassian.com/browse/AUTO-377 For now I believe your work-around is a good approach...as long as the comment is…

Hi @Kara Nadarajah Has your team enabled the "Enhanced board..." feature? If so, this is a known defect, and it appears ready to start development. Please vote for / watch the issue to see progress: https://jira.atlassian.com/browse/JSWCLOUD-25917 Kind regards, Bill

Hi @Katarzyna Radomska This symptom seems related to the problem of card content overlapping when there are many columns. https://jira.atlassian.com/browse/JSWCLOUD-25838 https://jira.atlassian.com/browse/JSWCLOUD-25839 I did not see a defect in the public backlog for the column titles and so I recommend working with your…

Hi @David Rawlins -- Welcome to the Atlassian Community! That symptom is a known defect, and it appears it is about to start development. To follow progress, please vote for / watch this item: https://jira.atlassian.com/browse/JSWCLOUD-25917 Kind regards, Bill

Hi @David Tieman Yes, that appears to be a known defect. You may vote for / watch it here to see progress: https://jira.atlassian.com/browse/JSWCLOUD-25917 Kind regards, Bill

Hi @Akhil Mishra and @David Vermeir This seems to be a known / open defect. There are several items for it in the public backlog, which you may watch / vote for to see progress: * https://jira.atlassian.com/browse/AUTO-12 * https://jira.atlassian.com/browse/AUTO-333 * https://jira.atlassian.com/browse/AUTO-759 Kind…

As those images are attachments, even sending links to them often only works for people with a Jira user license. There have been requests to add this for over 10 years, and often the response is to investigate marketplace addons. Unfortunately that would probably not help for emails sent from rules.

Hi @Milena Prieto -- Welcome to the Atlassian Community! First thing, context is important for solving problems with automation rules. I recommend posting an image of your entire rule, images of any relevant actions / conditions / branches, and an image of the audit log details showing the rule execution. Together those…

In the audit log, you can see a Show more link for each rule execution. Please expand that first one which shows as successful, and post what you see. That will show the issue keys and rule steps as they processed, and hopefully explain better what is happening.

I am unclear how else to explain this: The rule you have shown is triggered on a change to the Story point estimate field, but you are not using that field. Instead you are using time tracking for estimation. And so your rule should be triggered on a change the estimate field that you want to use.

Your syntax for setting a single-select user field seems incorrect. Please take a look at the linked documentation for an example.

Hmmm...You noted a couple of interesting things to me: * Each team has various aspects of the work * Each team needs visibility to any common information updates That makes me wonder if using an Epic to contain the common information would solve both needs, as the child issue for each team could be created, be worked…

Hi @Mane Zakaryan No worries, and I am glad to learn you figured it out! And as an FYI...as this is an older post, it can help to create a new question and link back to the older ones for context. Otherwise only the people mentioned or following the older threads will see it, limiting the suggestions you may receive. Kind…

Hi @Sarah Isaacs Adding on to Valerie's answer... Sometimes customers add / change their subtask issue types. Have you confirmed that your condition in the rule is checking for any of them, or instead check to confirm a valid type for this rule? For example, replacing issueType != Subtask with issueType IN (Story, ...any…

That feature and error message seem to be coming from a marketplace addon rather than from a built-in feature of Jira Cloud. And...the error message seems to indicate you are trying to export something that has not been added to the dashboard. I recommend contacting the vendor of that addon in the marketplace to get their…

I am glad to learn that helped. After the changes a few years back to user information, I believe that most JQL operations now require using the account ID values.

If you are using a company-managed project, were able to see / add the field to the view, and select that field in configuration, what options are available? If you see no additional options (such as "Go to field configuration") please check with your Jira Site Admin to further configure the fields.

Hi @Daniel Chirinos You could write a JQL expression to find the issues in the epic (i.e., have the same parent), and filter by the created date. To learn more about such JQL expressions, please see this documentation and free training from Atlassian: *…

Hi @Ankit Patel -- Welcome to the Atlassian Community! This seems an example of the consequences of storing multiple pieces of information in the same field. With out of the box features of JQL, I believe all you could do is search with the CONTAINS ~ operator if you know the exact release "date" expression. And even that…

I believe that is the normal behavior, as story points generally apply to a story (which is a valuable, releasable item) versus sub-tasks (which are a piece of a story and usually are not individually releasable). Although it is possible to make the field accessible for any issue type. If you scroll down in the issue…

Yes, and...I suggest taking a look at Kent Beck's new writings as he develops his book, Software Design: Tidy First, particularly the impacts of using agile delivery measures to assess people performance, team and individual.

Hi @Jake S If you drag-and-drop the NEW status into the TO DO column the backlog view will be removed and instead all those issues will be in the first column of your board. As the leftmost column for the board is the "not started", or To Do, column for a board, you cannot have 2 of those. (Just in case that is what you…

Hi @K -- Welcome to the Atlassian Community! Please review the date/time functions for JQL and you will be able to create queries as you ask: https://support.atlassian.com/jira-software-cloud/docs/jql-functions/ Kind regards, Bill

Hi @Ross Moulton -- Welcome to the Atlassian Community! Would you please post an image of your complete rule and an image of the audit log details showing the rule execution? Those will provide context for the community to offer ideas? Thanks! Until we see those... I hypothesize that the condition is not being met, and so…

Hi @Mohammad Gharehyazie -- Welcome to the Atlassian Community! The change log for a specify field returns that field, and so the syntax you are using may be creating some other string. Perhaps try: {{#changelog.Parent Link}}{{from}}{{/}} Kind regards, Bill

If you select the multi-select field with Issue Edit and do not select any options, it will clear it. If instead you need to remove specific values, you may want to use a JSON edit to use "remove" or: * expand all of the current values * remove the ones, as needed * format the result as JSON for a field update Here is the…

Hi @Allison Reece -- Welcome to the Atlassian Community! First thing, is this a single issue (work item) that just happens to display on two boards, and so it is copied...or is it two different work items for different teams? * If it is one work item, have you considered using one issue, and allowing the board filters to…

Hi @Ann Rumenapp To do that you would need an additional rule, using the generic Issue Updated trigger, followed by a check on the changelog to determine if the parent field was cleared. Then you could update, as needed. Here is some information on the changelog to help you create the advanced compare condition you will…

Thanks, @Teresa_DevSamurai And for a couple more... Automation for Jira rules, to help teams reduce repeated, manual work tasks: https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/ And for Product Owners trying to manage ideation and road-mapping larger efforts, see Jira Product Discovery…