Mikael Sandberg Community Champion

Hi @Shanmuga Priya, Welcome to Atlassian Community! Team-managed project do not have permission schemes, that is only available in company-managed projects. TMP only have three levels of permissions, private, limited and open: In order to see reports go to Project settings > Features, from here you can turn on the Reports…

You are correct, you would need to change the permission scheme used by your projects so you can control how have access to each project, and this is done either via groups or I would recommend that you use project roles instead to decide who can browse the project. That way you can control that access from within each…

That is a fairly simple automation to create, something like this should do it:

Okay, so you need to map your Asset org to the number that JSM is using for the Organization field (much similar to user picker fields that takes the user's Atlassian ID). If you go to Customers in your JSM project and click on an org you will see that the URL ends with at number…

Your JSON that you are using is missing "" around the smart value, try this: { "fields": { "organizations": {{lookupObjects.Organization (Jira)}}" } }

It should be pretty straight forward, all you have do is add the lookup object component and set it up to search your object schema and then use the selected unit to find the object. Then you can use {{lookupObjects.Organization}} to set Organization. Something like this: In this case I am looking up departments based on…

Yes, that is possible. Basically you make both fields required, but the second one is added to a section that is conditionally shown based on what the user selected in the first field. Something like this: The second field will only be required if that section is shown on the form.

Okay, so I did some testing and I believe the resolution is not set because it is the create action. You could work around it by setting an automation that sets the resolution after the request is created.

There is an HR template that has request types for both onboarding and off-boarding. I have a HR project that we use for just that, besides other HR things like general questions, promotions/transfers etc.

Hi @Jacob Smith, Welcome to Atlassian Community! Try moving the post function that sets the resolution to the top and see if that helps.

Hi @Giulia Silvia Canhete Rocha, Welcome to Atlassian Community! To add a new custom field, the first thing you need to do to is create it. During the creation of the field you will be asked to associate it with screens. These controls which fields are available when you create, edit and view the issue. Once the field is…

Your match is removing DESC and the time stamps because the match function is only returning the first one as stated in the documentation. Performs a regular expression search and returns the first (and only one) matching regular expression group. Try using \S+\s\S+ and see if that helps.

Hi @ikenna, Welcome to Atlassian Community! Currently Forms is not integrated with Slack, so the only way you would be able to get the Forms fields to appear in the Slack form would be to add new Jira fields to the the request form and then link them to the Forms fields. There is a suggestion to add an integration to…

Hi @BP, Welcome to Atlassian Community! You may want to take a look at Jira Product Discovery which lets you capture and prioritize ideas.

The way your automation is configured it is trying to get the fix version from the linked issue, not the issue that triggered the automation. Try using {{triggerIssue.fixVersions}} that will get the fix version from the issue that triggered the automation.

Is the field available on the Create screen? Automation can only set/edit fields that are available on the screens.

Currently that is only possible if you link the form field to a Jira field. Atlassian is about to release an API for forms, currently on track for Q2 2023 so pretty soon. It wouldn't allow you to tie the automation to a specific form field, but you could check the field based on an action on the request the form is…

Is there a reason those two files can be added to the same attachment field, since you can add more than one attachment to it?

The only way would be to use the REST API to get the users within an organization. The endpoint you would use is this one, Get users in organization. You need the organization ID, which you can get from this endpoint, Get organizations. admin.atlassian.com can export all your portal customers, but it would not give you the…

It could, does the response have a reference to the automation that created the post? If not, does the response have a reference to the issue that created the post? If the response has a reference to the automation you can delay the automation until you get the response back and then use {{webResponse.body} to extract the…

You can only have one attachment field on a screen and there is no option to add a custom field that can accept attachments. Is there a reason why you cannot tell the user so add multiple attachments in the attachment field?

@Danny J Quinn There are multiple suggestions to either allow epic name to be synced with summary or make it optional, for example here is one when Jira Software was an app called Greenhopper, JSWCLOUD-8215. I for one is glad that this change is finally happening, I have always told my users that they should make the…

NextGen isn't a term anymore in Jira, that changed to team-managed project (TMP). The KB you found about rules are for the new workflow editor that is coming out, you no longer have conditions, validators, post functions etc in it that you currently have in the old one. And if your project is a TMP JSM project you do have…

Hi @Logan Cummins, Welcome to Atlassian Community! Epics in a team-managed project doesn't have Epic name, it is using the Summary as the name, similar to the change that is now rolling out the company-managed projects.

So the {{issue.multiselect}} would be the name of your custom field. You can either use the display name, or if you have multiple fields with the same name, or if you may end up renaming the field in the future, you can use the custom field ID instead. You can get the ID if you go to Settings > Issues > Custom fields and…

Correct, what you want to do is done via issue security. Have a look at this KB for more information. Basically what you need to do is: * change the project permissions so you grant access to users to set the security * create an issue security scheme * add security level(s) to the scheme * add members to the security…

Hi @Christopher Moretti, Welcome to Atlassian Community! The automation for this should be pretty simple to do, something like this would do it: Just add a "Compare two values" condition for each value in your multi select that should generate a subtask. Because in this case I use subtask it will automatically be linked to…

Hi @Nils Bertrand, Welcome to Atlassian Community! No, currently it is not possible to do this in automation. Atlassian is working on releasing an API for forms that is scheduled for Q2 2023 according to the public roadmap. I have a similar use case and I am using Assets to work around it. In my case my form has a field…

@Sergio Gattás It would look something like this: In this case I would use the scheduled one with a JQL that selects just a subset of your epics at the time since the automation would be throttled if it runs for too long.

If you have set up your JSM to automatically share new requests with the customer's organization then they will be able to see all issues for their organization if they go to Requests in the portal. If you want more/different reporting then you would need an app from the Marketplace that allows you to add reports to the…