Bill Sheboy Expert

Hi @Emiliano It appears this issue was logged as a defect for Automation for Jira, with no workaround. Which means the API is broken most likely also. https://jira.atlassian.com/browse/JRACLOUD-75838 Best regards, Bill

Hi @Ken Taylor Looks related to this suggestion, tied to the parent new issue view ticket: https://jira.atlassian.com/browse/JRACLOUD-69574 Best regards, Bill

Hi @vildana_ermaya Would you please post some screen images of what you are describing? That will help the community provide more relevant input to you. Thanks! Best regards, Bill

Hi @marco espinoza That scenario should be possible for a rule which runs in the global context; those can span multiple projects. Please note there are limits to the number of executions of global rules, depending upon your Jira license level and when you purchased Jira. Currently only Premium license holders get global…

Hi @manas Sahoo -- Welcome to the Atlassian Community! The trick here is to gather the existing components first, and then append your new value. Then use advanced edit with the JSON as you note. Remember that the component must already exist for the project. For an example rule: * Trigger: manual (or whatever you need) *…

Hi @Neil Rafol -- Welcome to the Atlassian Community! The epic colors seem to drive the color bars on the roadmap. If you are okay with changing your epic colors you could use an automation rule to drive changing the colors using advanced JSON editing: { "fields": { "customfield_10011": "ghx-label-1" } } You may find the…

Hi @Daniel Egan -- Welcome to the Atlassian Community! What do you mean by a "timer"? (1) If you just need to know how long an issue has been in a current status, there is a built-in feature to classic boards: Days in Column. You may learn about how to enable that feature here:…

Hi @María Domene Are you asking about documentation on the Jira software product, or about creating documentation for your own products, or something else? For Jira cloud documentation, please look here: https://confluence.atlassian.com/cloud/atlassian-cloud-documentation-744721592.html If you want to create your own…

Hi @Laura Randall -- Welcome to the Atlassian Community! Would you please share a screen image of where you are entering release notes today? I am wondering if you are using some add-on feature. The release notes that I am aware of for Jira project releases are configured on the releases page, not on the individual issues:…

Hi @Ellis Carvalho "Yes, and..." to what @Guilhem Dupuy and @John Funk are saying: there are no best practices here, only better ones for different situations. Each of these tools can help solve automation needs, and what you problem you are solving may drive which to use. For example, to limit a status transition workflow…

Thanks for explaining your date definitions, which appear to match this timeline: <----------------------------> + "Start Date" "End Date" "Due Date" As you confirmed, Jira's Due Date is used on the roadmap to show the range of time for a work item, and other dates are not displayed. Without any possible marketplace…

Hi Renato, If you want both of those dates to display on the roadmap, that may be more than the basic roadmaps can do. I suggest that you investigate the advanced roadmaps (with Jira Premium version) or look at marketplace for add-on ideas. Out of curiousity, is your definition of "End Date" meant to indicate when a work…

Hi @[deleted] -- Welcome to the Atlassian Community! Nic explained why you cannot use epic swimlanes without the stories to connect the sub-tasks to the grand-parent (epic) on a Jira board. And, I wondered: if your team believes that you do not need the stories on the board, perhaps your team could work with fewer…

Hi @fridok Yup, that looks like a defect and I just reproduced your results with Chrome Browser. It appears that whatever the last search was run is being shown rather than the selected release set from the gadget. I did a quick check and did not see this in the public backlog. Please consider asking your site admin to…

Hi @panij.c -- Welcome to the Atlassian Community! In addition to Nic's question, I see you note an idea about a Kanban roll-up board. Have you tried to create such a board to include the work spanning the different projects? Best regards, Bill

Hi there... quick aside to the issue of different numbers of board columns, depending upon the board creation path. There is an open defect for that behavior: Different Columns in Boards with Create new board vs. creating board within a project https://jira.atlassian.com/browse/JSWCLOUD-21163 Best regards, Bill

Hi @Renato Francesco Miracco -- Welcome to the Atlassian Community! I believe that basic roadmaps (like in the Standard edition) rely upon the Due Date field. As a work-around, you could use changes to the custom date field to set your Due Date with an automation rule. For example: * Trigger: your custom field changes *…

Hi @simone.degregori You may want to email the vendor directly for this question. Here is their support information on the marketplace pages: https://marketplace.atlassian.com/apps/1221281/async-poker-remote-planning-estimation?hosting=cloud&tab=support Best regards, Bill

Thanks, Dan. If you are trying to edit the parent for a sub-task, it does not appear to be possible yet. I found that looking at the advanced JSON help and using a REST API call to gather the editmeta data for a sub-task. https://support.atlassian.com/jira-software-cloud/docs/advanced-field-editing-json/…

@Baris TEKELI I cannot tell from the posts if you are using the Cloud or Server version...In either case... I you plan to leave the text field in place, and people can continue to edit the field... Have you considered using a simple automation rule to automatically left-pad the field with zeros? Then a simple string sort…

Hi @Nick Thoman Please try this to access the first item in the list: {{issue.Testers.first.accountId}} Here is the documentation to learn more about handling list fields: https://support.atlassian.com/jira-software-cloud/docs/smart-values-lists/ Best regards, Bill

Hi @Daniel Newman For some context, would you please post an image of your entire rule? Thanks! Is this for a classic or a NextGen project? Next, if you log the {{Parent}} to the audit log, what do you see? Best regards, Bill

Hi @Saxon Julian You appear to be using a NextGen project, so you need to disable estimation so the counts are issue counts. To do so: * On the left slide-out pane, select Project Settings * Then select Features * Find Estimation, and disable it * On the left pane, select Back to Project * Check your numbers on the backlog…

Hi @Nick Hays That doesn't seem possible yet. There is a suggestion to copy all changes to linked issues: https://codebarrel.atlassian.net/browse/AUT-756 Until then, you may want to reconsider how your issues are organized / populated if there is that much information you want duplicated across the levels. Perhaps it may…

Hi @Florian Warncke -- Welcome to the Atlassian Community! Yes, you should be able to do that. The technique I found was to sum up the trigger issue's time spent as seconds, and then convert it to minutes. For example: * Trigger: manual (I used this for the example) * Branch: for epic (parent)* Action: edit issue fields,…

Thank you for clarifying that, and I look forward to seeing the answer to this one. __Bill

Hi @dharper Just to confirm, are you staying that the field I&B Team can contain multiple values, and that for each specific value found you want to add a label? If so, you can restructure your rule a bit with additional If/Else conditions and add some Re-fetch. That will slow the rule down but it should work. For example:…

Or, is the question about when the stories within the feature which are in progress? * Select all the Features * Where the project = X * And the Status = Funnel * And there exist Stories in the Feature...* Where the Story Status= In Progress If so, that is not possible with out-of-the-box, JQL. It would require a scripting…

Greetings community! The Scrum Framework has continued to evolve over time, and the current, up to date explanation may be found in The Scrum Guide, provided by the people who developed the framework: https://www.scrum.org/resources/scrum-guide As Scrum as evolved, things which were originally in the framework have been…

@Yerbol Nisanbayev thanks for your thoughts, and please consider that JQL could be made more SQL-like (and feature enhanced) without losses in some of the noted risk areas. Complexity: there appears to already be an alias parser for JQL to the implementation naming of entity/attribute naming, so no improvements needed…