Mikael Sandberg Community Champion

You could control it a little bit by modifying your allowlist/blocklist for specific domains, but that would be sort of a never ending battle.

Yes, if you are allowing customers to share a request with any email addresses then you would also have to invite them to your instance so they can see the request. It's sort of a catch 22 moment...

The share option is not linked to how customers can sign up. You can allow customers to sign up by themself, this is controlled from Settings > Products > Customer access On the project level you can control how the customer can share the request, so you could limit it to only allow the customer to share it with the…

The site access used to be under Products > your site > Site access, and from there you used to be able to say what products a user get when signing in for the first time. If you go there is should take you to the new location and from there you can control the access.

Hi @dominicjensor23, Welcome to Atlassian Community! Because this is a public community, I removed the URL that you included. You need to contact your admin for your instance regarding adding apps to it. This is a community for Atlassian products and most of us on here are customers and do not have access to other…

If you go into the issue you should see the Actions section on the right-hand under More fields, from here you should see automations that triggered on the issue.

Currently the form do not support showing the icon of the asset, it will only show the name. I did a quick search and couldn't find a suggestion for it, but hopefully the form will support it in the future.

Hi @Emily Combs, Welcome to Atlassian Community! A project is housing a collection of issues that are needed to completed in order to achieve a specific goal. A board is just a tool within the project that allow you to manage those issues. The board lives within a project, but you could use the board to manage multiple…

Hi @Yorben, Welcome to Atlassian Community! Please forward the emails you get to https://www.atlassian.com/trust/report-abuse so Atlassian can take care of it. 

Short answer is no, the free plan does not allow you to set permissions that limit the access to projects. You have to upgrade to at least the standard plan in order to be able to make changes to project permissions and get access to issue permissions if you need to limit the access further.

Correct, before Jira 7.0 you could go with a lower number of DC users, but as of 7.0 Atlassian set the lowest limit to be 500 users. At the time the price difference between Server and DC at 500 was minimal so it was a way to get Server customers to switch to DC.

Okay, so I think the .0 in the smart value is the issue. The AQL is expecting an integer, not a float. And that is why it works when you replace the smart value with a number in your tests.

Hi @William Qi, Welcome to Atlassian Community! My guess is that {{quantity}} is empty and that is why your automation is not working. How do you set {{quantity}}? I would add a log action after you set it to make sure that it has a value. 

Hi @Ken Pieschke, Welcome to Atlassian Community! You need to be Project Admin in order to get to it, and if you do have that access then go to Project settings > Automation. 

Everyone should have the new admin view, that has been GA for a while now, and the user access settings went GA sometime in May. Are you automatically adding users to the confluence-users group? If so then they should by default have access to Confluence since you have set that as the default access group.

You can configure the user access settings if you go to admin.atlassian.com under Products. You can learn more about it in this KB.

This is expected, Confluence just rolled out the new publishing experience as announced in this article, 🔅 A better publishing experience is coming to you 

As long as the page that have unpublished changes has been published at least once then those unpublished changes will stay and applied when anyone publish it even if the user has been deactivated. Personal spaces stays, and would have the same space permissions as other spaces that has been defined on a global level. The…

Correct, you would need multiple approval statuses, and then either have a custom field for the approvers for each status or you would have to clear the approvers field after each status. I have a workflow in our HR project that have 6 approval statuses for promotion/transfers, two of these statuses can be bypassed…

Hi @Hanz Rauch, Welcome to Atlassian Community! The Confluence Statuspage was just updated and there is an active incident being investigated. 

But the problem you will have when using a validator is that you cannot use Forms, since the data in it is not submitted until the request has been created. By doing it in an automation after the request has been created you remove that blocker and you control who the approver is, not the user.

In that case you would need something like Scriptrunner in order to do it, you should be able to create a scripted validator that does that. 

Currently you have to link that field to a Jira field in order to use it in an automation. Once the API for Forms is released you could use the API instead of linking the fields to get the date from the form and take action on it. 

Have you assigned yourself a JSM license and also added yourself to the role Admin or Service Desk team for the project? 

"Hide when empty" fields will aways be shown after visible fields, and based on the order that they appear in on the issue layout. The only way around it would be to pin the fields you want to see at the top. Note that pinning fields are per user, there is no setting that would allow you to pin fields for all your users.

Hi @Rob Lawson, Welcome to Atlassian Community! Yes, that is possible, as long as you are using company managed projects. Boards are controlled by a filter that tells the board what issues it should display, so you could create a new board that shows all the issues you want to see. 

You could do this with automation and the on-call schedule, and you would need to use an iPaaS since automation can only get a single user from the on-call schedule. I use tray.io to do this, and the workflow is basically an automation that triggers on issue creation that calls the tray.io workflow. The workflow gets the…

The tooltip is added at two places, both under Settings > Issues > Custom fields and also in the field configuration that the project is using. If you change the description under custom fields it will not carry over to the field configuration.

Yes, you would need to use smart values to figure that out and you have a couple of options. One is to do a diff in business days between now and the due date to see if it is within 2 business days like this: {{now.diff(duedate).businessDays}}

Hi @nico, Welcome to Atlassian Community! In order to the drag and drop on a board to work the filter that the board is using has to order the issues by rank. So go to your board settings and make sure that the filter looks something like this: project = JIRA ORDER BY Rank ASC