Bill Sheboy Expert

Comments

  • Thanks for that information; I am using Jira Cloud rather than Data Center and see something differently for that action. Let's try this: * in that field, type in {{issue.key}} rather than using the dropdown list * when that expression appears below the field, select it for use * test your rule to see if it links correctly
  • Awesome; I am glad to learn it is working! Please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!
  • Hi @Minh Luu -- Welcome to the Atlassian Community! Adding to Trudy's answer... Team-managed projects (TMP) have different reports available compared to Company-managed projects (CMP). Please look here to learn which ones are available for TMP and how they may be…
  • Hi @Juergen Koeck For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule, * images of any relevant actions / conditions / branches, * an image of the audit…
  • Hi @Frida Gustafsson Adding to the suggestions from @Marc -Devoteam- ... The numbering format for your versions will determine the logic needed to increment versions. For example, if your minor versions increment up until some maximum (e.g., 12) then additional logic is needed. Please see this other post for an example of…
  • Hi @Prachi Bolar As an Atlassian team member, why are you referring someone asking a question about Jira features to a marketplace application when there are built-in features which can do this? Please review the documentation for the Sprint Report to learn…
  • Hi Julia, When you link the issues to "Most recently created issue", that is relative to the last issue created. As you are branching to the first one, Task 1, you could change the link to "Current Issue" as that will refer to the "branched to" issue. Kind regards, Bill
  • Hi @Mikael Sandberg FYI...once the issues are read within an automation rule (e.g., with Lookup Issues action and JQL) the sprint field in the first issue could be filtered for the "active" one to get the sprint's end date: {{#lookupIssues.first.sprint}}{{#if(equals(state, "active"))}}{{endDate}}{{/}}{{/}} That value could…
  • Hi @Laura Hanna You note a team using Sprints, and so they are likely using Scrum practices also. Rather than sending a reminder email, why wouldn't the team already know which User Stories are done (or not) when they have their Daily Scrum (i.e., standup) together? Kind regards, Bill
  • If you were using Jira Service Management, with a Premium or Enterprise license level, there is a built-in automation rule action to create a Slack channel for an incident: https://community.atlassian.com/t5/Jira-Service-Management-articles/Automation-Rule-for-automating-incident-communications-in-Slack/ba-p/2878846 If you…
  • Thanks for those answers, and... Please post an image of one of the Clone Issue actions. Please note that if a field is not selected in the action, the rule will try to copy it. If none of the fields are copied over, this could be caused by a timing / racetrack error issue. When the Issue Created trigger fires, it can…
  • Hi @Lucas Donizete Cardoso I do not believe there is is an automation rule trigger to update issues based on a Slack message. Instead the issues are selected from Slack for updates. For example, with the default connector, you may add a comment to issues: * /jira TEST-123 * select to add a comment from the actions Kind…
  • Hi @John McDevitt -- Welcome to the Atlassian Community! Normally for an automation question, posting the audit log details helps to identify what is happening. Although with your rule structure, that may be difficult to follow check... Instead let's start with some clarifying questions: * Is your Product field a…
  • You are correct, and this seems to be a related symptom of the same defect. Here are the steps to reproduce it: * add a validator to the workflow to prevent transition if a select / option field is empty * save the workflow changes and return to a JPD board view * from a JPD board view, with columns as Status, select an…
  • Interesting! Let's see if one of the community managers can look at your watch configuration / the logs to learn why it did not notify you. I believe you could ping them with this email address: communitymanagers@atlassian.com UPDATE: I posted too soon, as it appears notifications have been down since at least 1000 Pacific…
  • Before proceeding, please confirm you have the correct smart values (or custom field ids) for your custom fields. Smart values are name, spacing, and case-sensitive. When an incorrect one is used, it evaluates to null. To find the correct ones, please use this how-to…
  • If you expand the details in that change notice, it lists the bulkfetch endpoint, although I do not find it listed in the documentation for bulk operations: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-bulk-operations/#api-group-issue-bulk-operations Perhaps try it to observe what happens.
  • Hi @Monique vdB Are there also content guidelines for the vendors in the marketplace listings for their products? If so, where could those be reviewed? I am specifically wondering if there is a requirement for products in an Alpha or Beta release phase, and which will transition to paid license products, to disclose that…
  • Hi @Sushil Ranjan What have you tried thus far to solve this need? If you have an automation rule that is not working as expected, please post images of the complete rule and the audit log details, and explain what is not working as expected. Those will provide context for the community to offer suggestions. If you have…
  • Hi @Vikrant Yadav Without seeing your specific call, I hypothesize you are also trying to pull back the fields at the same time, and so the results are limited to 100 issues. When only the id values are requested, the limit is up to the 5000 limit, when supplying the maxResults parameter. To pull back more issue fields,…
  • Hi @Verma, Shivam -- Welcome to the Atlassian Community! As Trudy describes, context is important for automation rule questions, so please include images of your complete rule, the audit log details, and explain the problem you are trying to solve. For such types of rules, it also helps to use the Log action to write…
  • Thanks, Rob. "See all notifications" under the bell icon has been stable for me for a while, although it occasionally still has a complete halt in updates...or shows the wrong date / time (where the posts are in order by the date / time value is wrong). One recent "change" I have noticed: sometimes multiple posts to the…
  • Hi @Rob Horan Just to confirm the context, are you missing notifications in: email alerts, mobile alerts, the bell icon / notification list in the community, something else? For myself, I gave up on the email and mobile alerts long ago, and now only use the notification list (under the bell icon). This is not 100%…
  • Hi Sue, In this Atlassian Community, people gather to learn and help one another on a volunteer basis. Thus, people help when they can. There are no expectations of when they can / cannot offer time and help. If you have more urgent timelines for support needs, I recommend starting with your Jira Site Admin to learn what…
  • I am glad to learn it is all working! Please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!
  • Hi @Chad Bellan For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule, * images of any relevant actions / conditions / branches, * an image of the audit log…
  • Yes, and... I have not found a consistent method to test for "empty" fields in automation rules, as they are impacted by the field type and starting conditions, such as: * field is empty * field is blank * field was not empty, and now is empty * field was not blank, and now is blank * field is a type which is never empty;…
  • Hi @Selvam A First thing, context is important for automation rule questions. Please post an image of the audit log details showing the rule execution, for both the first update and a later one. These will show if the rule is executing all the steps you expect. Next, smart values are name, spacing, and case-sensitive. When…
  • Hi @Utkarsh Agarwal With the approach you described, one could use a Jira Automation rule with an Incoming Webhook Trigger, and then send the notification by email, Slack message, etc.: https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Incoming-webhook And...I believe this approach will only…
  • Hi @Alexandr Rather than using the Create Version action, the rule could use the Send Web Request action to call the REST API endpoint for creating the version. Here is a how-to article for calling a REST API endpoint from a…