Nicholas Ellis _ALM Works_ Atlassian Partner

Hi Bernard, There are definitely a few ways to do this. I would suggest using size() to check if the labels are empty. Something like this: if labels.size() = 0 : "EMPTY" This works because the list of labels is treated as an array. Here is the documentation for our array functions if you are interested to learn more.…

Hi Joni, Currently there is not a way to do this, but I will definitely take this feedback to our team and see if we can't have this look a little cleaner in a future version. Cheers, Nick [Tempo/ALM Works]

Hi Eugene, If you group your epics by their parent link then you can do this very easily with a formula like: if type = "epic" : PARENT{summary} However I'm guessing you only want the summary without actually including the issues in the board. If so I don't think there is a way to do this presently. Cheers, Nick [Tempo/ALM…

Hi Justin, If you take a look at the roadmap link above you'll see that this is the second item on the list, which is not completed. It took a bit to get to the top of the backlog, but I would expect it this year in Q3 or Q4. Cheers, Nick [Tempo/ALM Works]

Hi Kenny, This should be pretty simple to do. Here is some code to get you started. with diff_days = DAYS_BETWEEN( MAX{due_date}, due_date) : IF diff_days > 0 : "max child due date early" ELSE IF diff_days < 0 : "max child due date late" ElSE IF diff_days = 0 : "child due_date matches parent" You should simply be able to…

Hi Ben, There might be some fancy JQL way to identify issues that have had certain labels removed or added, and then you could count them in Structure, but there is not a nice way to do this with Expr formulas at present. This will be possible once history is available in Expr. Cheers, Nick [Tempo /ALM Works]

Hi @Benjamin MAUREAU, Welcome to the community! This is how I would go about this. Here is a formula that counts the recently moved to Done issues: COUNT{ IF DAYS_BETWEEN(status_category_changed, now()) < 30 and status_category = "Done" : 1 } You could do basically the same thing with the in progress or "Doing" status…

Hi @Paule Longué, Welcome to the community! Here is the documentation for adding checklists to cards. Cheers, Nick [Tempo / ALM Works]

Hi @Andrew Horvatits, Welcome to the community! It looks like the article you linked shows how to do this. You simply need to edit the field to use the date range picker for the search template. Is there a reason you cannot or are unable to make this change? Or have I misunderstood your question? Cheers, Nick [Tempo / ALM…

Hi @tbriley, Welcome to the community! If you complete starting the sprint it should show the issues in the board if they are in the sprint. I would also double check that you don't have any filters active as 16 issues does not sound like much. filter documentation If not you can simply search for issues in that sprint…

Here is the correct documentation. https://support.atlassian.com/jira-cloud-administration/docs/create-edit-and-delete-users/ And you are correct there is not another way, only the invite method.

Hi @Erik George, This is possible, here is the documentation for manually creating a new user account in Jira. Cheers, Nick

Glad to hear it!

Hi @Silvia, Welcome to the community! This is the documentation to see this information on cloud. https://support.atlassian.com/jira-service-management-cloud/docs/view-the-email-processing-and-connectivity-logs/ If you're not on cloud you make need to ask your Jira admin for help. Cheers, Nick

Hi Melissa, You can save a search as a filter. Here is the cloud documentation. This will allow you to combine very general filters like all watched items with other more granular searches like: updated > "-1d"

Hi @Michael M, Welcome to the community! It looks like your JQL is correct. Here is the membersOf documentation. The value error may be you are returning assignees who are no longer valid, such as deactivated or removed accounts. Here is another answer about a similar problem:…

Hi @melissa holliday, Welcome to the community! It looks like you don't have your hosting type tagged here, but luckily it's not relevant for this question. In short you can search for these issues with JQL like so: watcher = currentUser() Basically this will search for issues that you (the current user presumably) are…

Hi @Oswaldo Peña Perilla, Writing a new answer for DC. Yes You are correct there is not anything in Jira OOTB to handle your situation. However there are several plugins that can address this. Here is an example search for "planning". Of course I do work for one of the companies that shows up in the search, specifically…

Hi @Sofia Grunspan, The expectation is that when you set the original estimate it sets the remaining estimate. However this only happens the first time, it seems in this situation you would only want to edit the remaining estimate. This is useful for determining accuracy of how close original estimates are to actual logged…

Hi @Juliann Otto, Welcome to the community! If all you want to have the QA team do is create tickets from outside Jira here is an article about multiple ways you can do that. https://community.atlassian.com/t5/Jira-articles/Five-Options-for-Creating-Jira-issues-from-Online-Forms/ba-p/845260 Cheers, Nick [Tempo/ALM Works]

Hi @Oswaldo Peña Perilla, You can configure non working days, here is the relevant documentation. Cheers, Nick

Hi Susan, You can include this as part of your Automation condition. It should look something like this: Cheers, Nick

Hi Mindy, This is possible, you'll want to look at the advanced issue workflows documentation. I believe the "Only Assignee Condition" fits what you are describing. Cheers, Nick

Hi Klaas, The issuelinks array is only available with Structure on prem currently. Your code is correct, but the platform is not. Here is the link to our cloud documentation. My apologies for the confusion. Cheers, Nick [Tempo/ALM Works]

Hi Klaas, The PARENT{} function returns whatever field is in the brackets. If it is empty I would expect it to return nothing. If it was something like PARENT{some_field}, I would check that the some_field variable pointed to an existing Jira field with data. If all of those things are true and it still doesn't work you…

Hi @[deleted] , Welcome to the community! These should be rather simple formulae to write. I would do something like this: if type = "Subtask" : PARENT{due_date} This will simply return the parent (story) due date field, but only on subtasks. The other one is a little bit more complicated, as it has multiple conditions. if…

Hi Marco, Welcome to the community! I would suggest that you create individual insert generators under each folder to insert the relevant versions underneath. Here is a simple Structure I made to demonstrate: You can add the insert generators by clicking the + next to "Automation", read more about it in the documentation…

Hi Victor, The short answer is yes this is possible, but it did end up being rather complicated to implement. Here is the code I came up with: if !count_sub_items: // if we are at a leaf (no children) with child_keys = PARENT{ array#subtree{key}.FILTER($ != this.key) }: // grab the child keys from the parents perspective…

Hi Kota, This is actually really easy. All you need to do is change #children to #subtree. The children modifier means only direct children (i.e. one level below). The subtree modifier will search the entire subtree (i.e. all levels below). Here is the documentation if you are interested to learn more. Cheers, Nick [ALM…

Hi Kota, Your code is really close, you just need to add the size function, to return the number of occurrences, instead of the unique list of assignees, like this: IF type = "epic" OR type = "story" : VALUES#children { assignee }.unique().size() Please let me know if you have any other questions. Cheers, Nick [ALM Works]