Bill Sheboy Expert

Hi @Hassan Mahini -- Welcome to the Atlassian Community. Short answer: no, that is not possible as you described The version list can be reduced by archiving old versions. For both versions and components, there are several suggestions to limit the drop-down lists to the scope of the project. I did not notice any…

Hi @Raghu G -- Welcome to the Atlassian Community! I do not believe that is possible with out-of-the-box features. Some alternative options are: * investigate marketplace addons for JQL, etc. which support calculated fields * investigate Automation for Jira options to perform the concatenation. Automation for Jira is an…

Hi @Nallusamy Narayanaswamy First thing, I am using Jira Cloud and cannot verify the following... My understanding is those user macros are based on JQL, which out-of-the-box cannot perform such operations. Perhaps if you have one of the marketplace addons for JQL which supports calculated fields it is possible. Kind…

Hi @Irina Svirkina First thing, I am just a Jira user and not a representative of Atlassian in any way... I suspect the answer is: "no, that is not possible". If any marketplace vendor could add to that information, or even allow customers to configure it, it seems like it would steadily get longer and longer/more and more…

Now that I think about this...another way that might work is to expand your versions into a list with your own delimiters, iterate the list, use a regular expression with match() to find the desired name (which can use smart values as params), and then check the archived attribute. Please note, I have not tried this.

Hi @Aaron Baff -- Welcome to the Atlassian Community. That does not appear to be possible yet. There are several suggestions to make this more configurable/adjustable, such as this one: https://jira.atlassian.com/browse/JRACLOUD-68648 You may watch/vote for it to see progress. Kind regards, Bill

Hi @Hardeek Patel -- Welcome to the Atlassian Community! Yes, and...to Mark's answer: There are a couple of suggestions to add a "move action" for automation, which you may review below. Move is not supported in the REST API and there are quite a few possible problems, requiring human interaction, and so it probably would…

Hi @marcel.schmid One work-around I have seen for people-helping the Assignee is to add a multi-select custom user field, such as Additional Participants. You would need to perform your own dependency and reporting analysis (probably with JQL) to use it. Kind regards, Bill

Hi @David Leal I wonder if this symptom is related to the deprecation of some Epic's fields with the move toward "Parent" for all the relationships. Definitely Epic Name is on that list, and will only use Summary later. Perhaps this has already started for the REST API which drives Jira Cloud for Sheets. Some of the…

Hi @Mohit -- Welcome to the Atlassian Community! I am unclear on your use case, and it seems you want to automatically trigger some form of testing process and have that process update an Excel file. Is that correct? If so, you may need to specify more details for the community to help, as you do not indicate how that…

Hi @[deleted] The function asJsonObjectArray() is not finding the "id" key as you have already dereferenced to accountId, and so it returns null. Please try with {{initiator}} and instead of going to the accountId attribute first, convert to JSON and then replace the key. Something like this:…

Hi @Benjamin Budian -- Welcome to the Atlassian Community. First thing, I am just another customer and not with the Atlassian team... As you note on some of your screen images, the free plan level does not support configuring roles, advanced permissions, etc. Please look here for more information on the plans and if you…

Hi @Vinay S -- Welcome to the Atlassian Community! Which instructions were you using and what are you observing? Also you posted this in the automation area, so if you have an automation rule which is having problems please consider posting images of your rule and audit log details. That will provide context for the…

Hi @Omer As the other question to which you linked is "solved" what do you think of marking this one that way too? That will help people to see this issue has been addressed. Thanks, and kind regards, Bill

Hi @Patrick Howell I am curious: what is the purpose of creating a parallel community/newsletter/etc. on Jira automation separate from this group? Kind regards, Bill

Hi @[deleted] Without seeing your complete rule, perhaps a couple of things to try are: Cloning doesn't necessarily link everything you want, and so perhaps try to add the link from the source issue afterwards, using Branch on Last Created Issue and referencing the links in the {{triggerIssue}} If that "mentioned in" link…

Hi @Dennis_H That is odd...definitely weird permissions things can happen in Jira when someone in key roles is marked inactive. What do you observe if you change the Project Lead to an active user, such as yourself? Kind regards, Bill

HI @Arnav What do you mean by automatically propagate labels? You could do this with automation rules, or possibly marketplace addons. To do this with automation rules, please ensure you cover all the scenarios which are relevant to you. For example: * Labels changed in an existing epic with child issues * Issue created…

Thanks, Anna. It would seem the issues are encountering a couple of things: Hide completed issues is using Updated versus Resolved: https://jira.atlassian.com/browse/JSWCLOUD-21897 And for Jira Server, Hide Completed issues is impacting columns other than the last one on the…

Hi @Sina Sultani What have you tried to do this? Please provide your JQL to provide some context. Given the current Description field markup, it seems you may find heading markup with: project = myProjectName and description ~ "h1." You would need to clauses for any of the levels you use, such as: project = myProjectName…

Hi @mgeiger -- Welcome to the Atlassian Community! What do you mean by "worked on by another person"? For example, if you mean an issue was ever assigned to someone other than the current user this could help: assignee WAS NOT currentUser() AND assignee IS NOT EMPTY Kind regards, Bill

Hi @Arnav Please consider creating a new question, and perhaps linking to related ones. That will ensure more people see it...only the people currently following this thread will see it otherwise. Regarding what you asked about... Are you using Jira Cloud or Server/Data Center version? If on Cloud, what is your project…

Hi @Anna Bartczak Your image of the board is truncated. Would you please show the entire image to show if any of the quick filters or people/assignees are selected? Selecting a quick filter or assignee would definitely hide some issues. Also, have you tried to use advanced search to view the issues which are not displaying…

Hi @jpineda In my opinion, how your team chooses to work is what you agree to do. Jira is merely a tool to help visualize and manage your flow. The symptoms you describe may be a communication/semantics issue. You describe "Assigned" as what many teams might call "Building". That is, your flow steps names indicate "we…

Hi @Steph Bannister For the first option you noted, you could use the Manage Watchers action to add/remove people. If the values are in a field, just use their account ID smart value from the field for the removal. If mentioned in a comment, you could use a regular expression to extract their account ID and then remove…

Hi @Matteo Cristiani -- Welcome to the Atlassian Community! Apologies in advance for the long answer... For your first question, I do not believe nesting branches is supported. I have seen posts where people dragged a completed component (branch/condition/action) from one area of a rule to another, allowing things which…

Hi @Chris Mitchell -- Welcome to the Atlassian Community! There is no built-in planning poker feature for Jira Cloud. That screen grab appears to be this addon product from the marketplace: https://marketplace.atlassian.com/apps/1224759/agile-scrum-planning-poker-for-jira?hosting=cloud&tab=support I am not using that tool,…

Hi @MANISHA -- Welcome to the Atlassian Community! What have you tried thus far to solve this problem, as this is possible with an automation rule? Please post an image of your current rule and audit log if you are having challenges getting this to work. I expect you will need 3 rules to do this: * one triggered on the…

Hi @Jenn Sherman Yes, and to Mark's answer: Do you expect there to be multiple epics meeting such criteria, and if so what would you do? If you do not expect this, I recommend a slight change for some insurance... * trigger: scheduled with JQL * action: lookup issues with JQL to find the epic(s) * if/else condition:*…

Hi, Dan! Short answer: when you want to see issues for a filter, set fields/criteria on all the issues as needed, or adjust the filter accordingly Longer explanation: I understand how that behavior could cause confusion, but it is consistent: The filter criteria applies to all of the issues, regardless of their placement…