Dick Community Champion

Thank you @Bill Sheboy for sharing your knowledge regarding the additional ways that maturing teams can use to size and plan. It is greatly appreciated. Three is the magic number (the holy trinity). Kind regards, Dick

Hi @Pouchon Bontemp Welcome to the Atlassian Community Compatibility is organized the other way around: You enter the Atlassian Market place and search for the app you need, then look for the compatibility. Kind regards, Dick

Dear @Holly Hammond You received the perfect answer from @Bill Sheboy in your first edition of your query. He explained that the differences in the triggers would necessitate the 2-automation approach. It's highly unusual to start a new query the way you just did, it could've been a simple follow-up reply to the original…

Hi @Ravindra Mehta Welcome to the Atlassian community. Your problem can be fixed using an automation that checks the content of the field labels. As multiple labels can be given, this field is an array of strings. This answer has already been given here at the forums. Be advised though, that you can use compounds as well.…

In addition to what @Dirk Ronsmans mentioned, the organizational adminship is best taken up by at least two persons from within your organization, just to avoid problems regarding access in the future. It's a no-brainer we encountered ourselves a while ago. :) Kind regards, Dick

Hi @Nadine Ullmann Your best approach would be to schedule a daily creation of an story (for the department) with 3 subtasks (for each of the teams). A second automation would trigger on change of either count field in a sub-task, find it's parent and sum the two fields across all sibling sub-tasks of the parent work item.…

Hi @zain Welcome to the Atlassian Community! It's like @Vishal Biyani states, a second scheduled automation would be your best way to get the job done. To help you find the parent issue(s) from the first automation, you might want to mark these with a label, so that you can tell the second automation to especially look for…

Hi @Shamini S , welcome to the Atlassian Community! When upgrading, you definitively need to check the prerequisites to the underlying programs such as - you guessed it - Java. All software release notes come with upgrade notes. Upgrade notes for 10.0.x describe specifically something about Breaking changes to the Java API…

Glad you had that sorted out, @Laddawan P Kind regards, Dick

Does the filter query of the "malfunctioning" board query issues of projects where the user has no creation rights? Kind regards, Dick

The user should have a role that allows them to create issues in the project(s) the board is part of. Roles are defined in the Permission Scheme that is used for the project. Multiple user roles could be given the power to create issues. Kind regards, Dick

Hi @Radl Glück , Did you proceed with implementing the scheduled automation, or did you introduce the status describing the work transfer to the other team (and the underlying automation to generate the Jira work item in the alternate project) ? Just curious, Dick

Hi @Simone Di Giannatale , welcome to the Atlassian Community. Problems regarding plugins are best tackled by contacting the company that makes the plugin. You may find that they actually listen to their customers and are focused to making their plugin more resilient and error free. You can reach them via AppFire and their…

Just tried this out on the Cloud version. @John Funk thanks for setting me straight. Other custom fields seem to be exempt of this lack of support. I'll be up voting the ticket you mentioned. Kind regards, Dick

Hi @Ferry Portier Yes, this is possible. In the plan settings (cogwheel in the left-most menu), you can select the custom fields tab and add fields there. Kind regards, Dick

Hi @vaibhav bisht , Welcome to the Atlassian Community To my best knowledge (and documented on the Atlassian smart values page), lookupissues only support a limited set of properties; key, description, url, summary, assignee.displayname, reporter.displayname, status.name, issuetype.name, resolution.name, fixVersions.name,…

Thank you @Isabel Fonseca for reporting the answer to your problem. This way, it can help others with a similar problem too. Kind regards, Dick

It could also be a difference in the international languages setup and a present/absent i18t property definition in the workflow transition. Kind regards, Dick

Hi @Radl Glück Regarding your questions: ad 1: it will execute for each of the found issues, each triggering one creation of a ticket ad 2: you can always refer to these fields of the initial issue as triggerissue.key and triggerissue.summary ad 3: The linked issue field will be filled with the key of the created issue in…

@Rashmi Ratnani So all in all, the plans are more for upper management, whereas the story points are something team-specific. All manipulation of story points by upper management, can only serve a high-over scenario's, certainly not an individual capacity per team member. Sure, the two come together: when a team gets…

Let the beginner team start with chunks of work that they deem "are the same amount of work and complexity". That would give them the feeling of let's say 8 story points each (arbitrarily). See if the sprint goal is reached, and use the retrospective to evaluate the total amount of story points finished during that sprint.…

My problem is that this user is counted as having a license (and thirty others as well). I do not have control over this, which creeps me out a bit. Kind regards, Dick

This behavior is weird: * Checking with the user, he had no permission to enter Jira. * User has a "never logged in" status when looking him up. * I provide access by placing him in a correct Active Directory group * User has access and logs in for me 1 time * User has 1 inlog count with the correct date. * I remove access…

Hi @Mugilan Sukumar I don't know if this is still a pressing matter, nevertheless, this is the sql for a MS database, which should be good on oracle as well (or at least the majority of it) use YOURJIRADATABASE SELECT u.lower_user_name, u.created_date FROM cwd_user u WHERE u.active = '1' AND u.lower_user_name IN ( SELECT…

Normally, a user sync does inactivate the users that were excluded from these special groups we use in the Active Directory. The never-logged-in users should've been deactivated (I painstakingly went through all the nested groups and constructed a PowerShell script that would gather the persons in all referred groups. I'm…

Hi @Elodie Ferreira It's always wise to be one step smarter than your users, so I fully endorse going the extra check (could be a single condition in your automation) as suggested by @Bill Sheboy . Kind regards, Dick

Thank you for letting us know, @Elodie Ferreira. That surely brightens up the start of the weekend! Kind regards, Dick

Hi @Seenivasan K and @Trudy P Claspill Would moving the sub-task to a different "ErrorProject" with a single story (immutable key = ErrorProject-1) be a solution to not being able to archive or wanting to delete the obsolete subtask? Kind regards, Dick

Hi @Elodie Ferreira Welcome to the Atlassian Community The smart value in your second condition is a list of possible label entries and should not be treated as a single value. You should iterate through the list using {{#issue.labels}}{{/}} as per documentation on lists: Atlassian on list variables Kind regards, Dick

To be honest, @Jens Bode I could see from your workflow that you were very focused on capturing the actual way that you wanted to work in your team, within the Jira workflow. Don't be surprised if your admin will propose a workflow that: * has company-wide status names (that might not coincide with the names you had…