Bill Sheboy Expert

Please note that only the summary and status name are in that expression. I believe you need to supply the issue key (and / or HTML markup with the url field) if you want the link to be available.

Hi @Pender Fort -- Welcome to the Atlassian Community! No, it is not possible. Jira Product Discovery (JPD) is a product and is a type of team-managed project. Team-managed projects do not yet support Components. Please look here to vote for / watch progress on implementing that…

Hi @Saira The original question was to list the issues, and no more. Do you have an additional want / need? If so, I recommend creating a new question of your own, including images of your complete automation rule, the audit log details showing the rule execution, and to describe what is not working in your rule as you…

Hmmm...you may want to check if your distribution list accepts external emails. Regarding some references to try entity properties, here are some below. There have also been several community posts on using these with rules. https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Set-entity-property…

Hi @Javier Peraita Without seeing your complete rule, my answer would be "maybe". If you have a simple rule with no conditions or branches, what @Jehan Bhathena described will work to link the issues. But if your rule has conditions or branches, AND the issue is created inside of the condition (or branch), it is possible…

Hi @Matthias Miehl You may vote for / watch this issue in the public backlog to see progress on that suggestion: https://jira.atlassian.com/browse/AUTO-519 Kind regards, Bill

Hi @Eliyahu Klein Adding to this answer...another thing which can cause this problem is having the incorrect smart value for a field. Smart values are name, spacing, and case-sensitive, and when have the wrong one they typically return nothing / null instead of an error. To confirm the smart value for a field you may use…

Hi @karthik Hiremath -- Welcome to the Atlassian Community! As a reminder, the Atlassian Community is not a free labor pool to implement requests on demand, particularly in short timeframes. It is a community of users, helping and learning from each other. And using Jira automation rules requires both learning and…

Hi @Abhi To do what you ask, increment the value from the "most recently created story", you must first find the most recently created story. You appear to be using Jira Server / Data Center version of automation. The action Lookup Issues would make this easier, but that is still in progress of being…

Hi @Kunal Kumar I believe you have a typo in your expression. Please try: {{issue.customfield_10601}} If that does not help, please post images of your complete rule and the audit log details. Those may provide context to explain what you are observing. Kind regards, Bill

Hi @adrimars A couple of work-arounds you might try are: * outside of Jira: create an email distribution list (in your company email system) and use that, or * inside of Jira: create an entity property (perhaps at the project level) to store the list of email addresses, and use that. The first approach is simple, and the…

I believe the smart value expression I provided should work with Server / Data Center, as it uses not specific Cloud features. If you only have the user name and need the account id to set a field, there are not many options for Server / Data Center yet. I believe you would need to call the REST API with a web request to…

Hi @Lakshmi Kumari With the built-in features, you could do this by exporting the users and using their account id values. For example: * export all of the inactive users * grab their account id values from the export, and use those as a comma-separated values list * and then search for them with JQL, perhaps like this…

Hi @LynnG If you perform internet searches for the following terms you will find the Atlassian documentation, and may can compare those: * "Jira Cloud Scrum board documentation" * "Jira Cloud Kanban board documentation" Additionally you may want to create practice boards with free Jira instance, or in your company site, to…

My mistake; I missed you had not raised this as a new question. Please disregard my comment.

I am glad to learn that helped. Please consider marking this question as answered; that will help others with a similar need find solutions faster. Thanks!

Hi @Gilad Shtern The comments field is a list. Do you want this information from the last comment, or something else? If the last one, please try this: {{issue.comments.last.body.split("owner: ").last}} Kind regards, Bill

What is the field type for your custom field? If they are not both date type I wonder if the comparison using isBefore() does not work as expected. You can check this by writing the value to audit log (or checking the field configuration) Another thing to try is to use the same format for the two fields (i.e., your custom…

Hi @彥宏(Luke) 劉 The specifics of the rule will depend on your scenario. That is, which issue do you need to check / update. If you look at the expression I wrote above you can see how to compare an issue's parent due date to the current date (adjusted). To use that for an edit, type it in the edit field value, it will…

Hi @Vijay Byndoor First thing: I recommend creating a new question for this. Otherwise only the people following this old thread will see it. When you do that, please post images of your complete rule, the audit log details, explain what is not working as expected, and link back to this thread. Thanks! Back to your…

Hi @Quang Nguyen Did you try this with the Issue Commented trigger? When I did that, I saw the name of the attached file in the comment body. Perhaps try writing that to the log to see the format of the name for your use, as it could be parsed out using text functions or a regular expression. Kind regards, Bill

Yes, and...to further these ideas and learn more about improving flow, consider some additional reading like The Principles of Product Development Flow: Second Generation Lean Product Development, by Donald Reinertsen.

Hi @Nathan Given I checked the public backlog and did not see this symptom for scheduled triggers with CRON expressions in rules, but did see others (like firing when there was no data to process). You may want work with your site admin to submit a support ticket for this so Atlassian is aware of the…

Hi @de Angelis, Nicholas -- Welcome to the Atlassian Community! Your syntax to access the property is correct. And, I believe entity properties are stored as JSON blobs, so effectively as text for what you are doing. Please try converting with .toDate before using the value. I believe this will answer your second question…

Hi @Pourna Radha-Burhoo First thing: Jira queries with JQL return issues, not issue counts. You may get the count by querying the issues and looking at the results. Next, would you please clarify what you mean? That will help the community to offer suggestions. For example, do you mean: * What are all of the issues…

Hi @Jeff Gordon Yes, that is a known defect. You can watch / vote for it to see progress: https://jira.atlassian.com/browse/AUTO-406 My hypothesis is that when a rule changes (including disable/enable) it has a new, unique identifier and whatever logging it checks is now a "clean slate" for the duplicate comment checking.…

Hi @Abhi I suggest you create a new question, and link back to this thread. Otherwise only the people following this one will see it. When you do that, please post images of your complete rule, the audit log details showing the rule execution, and describe what is not working as you expect. That will provide context for…

When that web request, response comes back, I believe it is text and not typed, such as a numbers. The work-around is to force this into a number using a math expression containing an iterator over the issues, perhaps like this: {{#=}}0{{#webhookResponse.body.issues}}+{{customfield_XXXX}}{{/}}{{/}} If that does not work, I…

One more thing to try... Rules can get "broken" due to to many edits, problems publishing, etc. I have no idea why this happens. The check for that cause is what Jack suggested earlier: disable this rule, create a new rule with the same steps, publish, and test. If that does not work and you contact Atlassian Support,…

Not that I am aware of...You may want to also post this question in the developer community: https://community.developer.atlassian.com/ And as a suggestion: please try to keep your posts in the same conversation thread (that is, below the current one). That will help people who look at this question see if there are…