Mikael Sandberg Community Champion

No, if you remove the user from one spaces they will not be able to manage the board. Anytime your board included work items from different spaces they have to access to all spaces included. If the board had all statuses included, then take a look at the workflows, it could be that the next status is in a different column…

The reason behind this is that anyone can be approver, including customers, so if they can only access the portal they would not see the transition screen.

If you are using the approval feature in the workflow you cannot have a transition screen, as the warning you see is telling you. The only way would be if you remove the auto transition in the approval and instruct the user to manually transition the work item based on their approval/decline.

I have used automation for a lot of different scenarios, for example for promotion and relocation approvals, assigning tickets to specific teams, onboarding and off-boarding, getting data about the user from Okta, assign tickets based on on-call schedule in Operations just to mention a few.

You need to check your customer permissions, it sounds like your customer sharing settings allows customers to search those either within their space or organization. Does your external customers with gmail accounts belong to an organization within the space?

Yes, that is possible. Just make sure that you are setting the scope to be multi project and include both projects. Since it has to be multi scope you need to be Jira admin in order to create the rule. 

Hi @Mallick_ Anik, Welcome to Atlassian Community! A couple of questions, are all the statuses that both spaces are using linked to a column on the board? The user that had the issue, do they have the right access to both projects? If all the statuses are linked to columns then you have to start looking at the permissions. 

Hi @Hong Zhou, Welcome to Atlassian Community! I have notified the Atlassian support team that is on here, and they will reach out to you within 2 business days about this. 

And to your question to why it is limited to just 20 work items, if you look a the instructions that limitation is there to improve the quality of the response.

You can always edit the agent, or create a duplicate of it and change the limit if you like. The default agent is similar to Automation templates, it shows you have to create it, but you have the option to adopt it to your liking.

You would have to find a way of segmenting them, unfortunately.

@Stefan Draber Please create a new question for this and reference this question, instead of adding a comment on a 2 year old question.

As @Marc -Devoteam- mentioned, Test is just another work item type that Xray is using, so yes, you add the field from Space settings > Work items > Screens, just like any other work item types.

If you are on a free plan the only support available is to use this community. I have reached out the the Support team that is on here and they should contact you within 2 business days.

I have notified the Atlassian support team that is on here, they should be reaching out to you within 2 business days.

You can do this via automation, trigger the automation on when the SLA is about to breach and then use the Send Microsoft Teams message via webhook component to send the message. Checkout this KB for more information using Teams with automations.

Hi @Jeffrey Hagstrom _E_, Welcome to Atlassian Community! What you could do is break the automation into two, the main one does the lookup and then you use the For each smart value loop that calls the second automation that does the actual work on the object. 

Correct. That Id is unique for each page.

Instead of creating your own Id, why not use the page Id instead? It is a unique number for each page in the instance.

You can do this using the work item collector, it allows you to set a default user as the reporter. You other option would be to open up the space for everyone on the web, but you would then open a security risk, so I would go the collector route.

Is the field that they want to be required/not required based on previous answer linked to a Jira field? If not then you could add two sections that are conditional with one section making the field required. Without using sections you cannot make the field required/not required.

Yes, that is possible if you add a status attribute, you can then user a filter on the field that filters out users were the status is inactive for example.

Hi @Ed Anderson , Welcome to Atlassian Community! You have to invite your users, and if they belong to a verified domain they will show up under Directory > Managed accounts.

Sort of, you can use the Copy work item layout to apply it to other projects.

Besides the screen you also have a layout for the work item, which takes president over the screen. Try re-order your fields in the layout, located under Work Items > Layout.

You have a couple of options, one is to not use a board for each team and instead use the Teams field to indicate with team the work item belongs to and then have quick filters for each team. That way you only have to maintain one board and create sprints on a single one. The other option would be to use automation that…

I haven't used it, but at my previous company we would have used them since you can include both KBs and requests on the landing page. That was one of the reasons we moved away from the Portal and used Confluence instead because it allowed us to customized what the user/customer saw. So, a landing page would solve this…

Hi @bruno_camilo, Welcome to Atlassian Community! When searching on Day.io support it looks like the company is permanently closed, so that would explain why the app integration hasn't been updated since 2023. Based on that I would say that the integration has stopped working. 

Also note that Atlassian will implement limits on the number of options starting in September 2026, as announced here.

Technically there is no limit on the number of values you can add to a select list, but you will affect the performance once you go over 100, and that is why we suggest using Assets instead. If you continue down the road of using select list your only option to maintain that list is either manually or via the API.