Mikael Sandberg Community Champion

Hi @Joaquin Smucler, Welcome to Atlassian Community! You should be able to do this in Trello. Durning Team 21 there was a session on how Lawrence J. Ellison Institute for Transformative Medicine of USC is using Trello. At the moment I can only find the session details for…

The {{lookupIssues}} is a list, so all you have to do to get the size is to add .size to it like this {{lookupIssues.size}}. There are also other smart values that you can use with a list, check out https://support.atlassian.com/cloud-automation/docs/jira-smart-values-lists

Here is the property you can change to set the number of objects returned on a page, Paging 

On Bitbucket server you should be able to define the number of items returned in the pagination, 25 is the default value. Let me see if I can find where you set that, it has been a couple of years since I did that. Also take a look at this blog post, it shows how to use pagination to get all the repositories, BitBucket…

You can do this using automation. If you are a project admin, go to Project settings > Automations and create a new automation that triggers when a new issue is created. Then configure it similar to this one

Hi @Ender, Welcome to Atlassian Community! If you look in the Automation library there is an automation called "When a customer comments on a closed request → then reopen the request" which you could use and just change so that when the assignee comments, transition the issue to in progress. 

You should be able to do this by checking the size of the list and then configure your if condition similar to this

Hi @Kanad Chatterjee, Welcome to Atlassian Community! You can set a condition in the workflow used by your stories that will not allow the transition to completed to happen unless all subtasks are in a specific status. Have a look at Configure advanced issue workflows for more information. 

You can change the description of the field if you go to the field configuration used by the project. The description in the field configuration will override the one set under custom fields. If the project is using the default one, just make a copy of it and then change the description. Once done you need to associate the…

@Devin Haynes, if the issue types that you are moving between are using the same configuration the field values will be retained, but if you move between issue types that are on different configurations it will not retain the values. When you are using multiple configurations you can see it as different fields, the only…

Great article @Alex! Looks like some of your screenshots are missing/in the wrong place.

Everyone is everyone that have access to your Confluence, and it is controlled based on your global setting. If your space permissions limits who can access the space, say to only a specific group, then everyone would be anyone belonging to that group.

The short answer is no, portal groups cannot be added. to your requests. The group is not stored anywhere so there is no way of finding out from which group the request originated from.

Hi @נטע צויג, Welcome to Atlassian Community! To add a custom field to an issue type you have to associated the field with the screen used by the issue type. From the custom fields list, select the three dot menu and Associate to Screen, then select the screen you want it to be on. See Add a custom field to a screen for…

Hi @Taylor Turner, Welcome to Atlassian Community! The first thing I would check is that you have access to the space in which your coworker created the page. Then the next step would be to check if any of the parent pages have view restrictions on them, the easiest way to do that is using the permission inspector that you…

It does, if you use an external option to set the second field. Then you would just need to get value for field one, look it up in the csv, and send an update request back. Automation can only part of this, so you would have to rely on something like tray.io to do the lookup and either send the value back to automation, or…

Yes, you would have to run it twice, one for each field. Instead of using automation for this I would probably go with an external option, you can then use two lists to map the values from both fields.

No worries Chris, we have all been there. So the URL needs to contain the fieldID and the context ID, you can get both of these either from within Jira if you go to administration > issues > custom fields, or your other option is to get it via REST API. Once you have those two IDs you will also have to add two headers, one…

Yes, if you wait for the result to come back from the web request, you can get the value for the specific position and then use a smart value to set the second field.

It should be possible to get the value by using the Send web request to the REST API to get the value for the second field. You can find the API call to use here.

Something similar to this should do it. First do the lookup base on the serial number and then use the advanced branching to loop on the returned value from the lookup.

Thanks Angélica! Unfortunately this also prevent you from importing updates if the object has a reference to a user type attribute, even if you are not importing that attribute.

The way I would do it is to add steps in your automation that searches for the new object, and if it is found, add a comment in the request noting that the object was created.

The permission to create spaces is a global permission setting, so you can disable it from there so only admins can create spaces. Have a look at Manage global permissions for more information.

No, it should be pretty straight forward. As long as you do not add your customers as users in the JSM project they will not be able to see that project when they access a JWM project. We have a similar set up where our internal customers are using JSW for development, but they can only access our JSM projects via Helpdesk…

Yes, it is possible. Zendesk has an integration to Jira, but I believe that you have to manually initiate the link from within each Zendesk ticket. Your other option is to look at one of the two-way sync apps that are available in the Marketplace. We are using the app that comes from Zendesk and we are using it to escalate…

Hi @brindha.panneerchelvam, Welcome to Atlassian Community! Please check out this thread for the latest information regarding Log4j, https://community.atlassian.com/t5/Trust-Security-articles/Atlassian-s-Response-to-Log4j-CVE-2021-44228/ba-p/1886598 

The preset rules that you found in the documentation linked above is for Server/Data Center, not Cloud. On Cloud you have a library of preset rules that you can enable if you like.

Hi @Prod, Welcome to Atlassian Community! The resolution field tells Jira if the issue is resolved or not, and if you have that field added to a screen it will automatically be a required field. If you do not have it on your screen, make sure that it is not set as part of a post function until the issue has reached a done…

The columns on the board is based on your board settings, not on the workflow. If you go to Board settings > Columns you can rearrange your columns from here. You can also map your statuses from the workflow to your columns from here.