Mikael Sandberg Community Champion

On the request form you cannot have multiple attachment fields, but the attachment field can accommodate multiple files in it. If you really need multiple attachment fields then your only option is to use Forms instead, and it would look something like this: But the same thing applies in Forms, the attachment field can…

Hi @Candace Roberts, Welcome to Atlassian Community! Intents is similar to Answers in Halp, and you can use them to answer common questions. The way the Virtual Agent works is that it will first see if there is an intent that can answer a question, and if not then it will use Atlassian Intelligence and search the connected…

Hi @Kelly Sable, Welcome to Atlassian Community! When you enabled the virtual agent for the Slack channel, did you also enable AI answers? Also, check your settings for the KB, it should be set so everyone logged in can view the linked space. 

Short answer is no, JSM does not have the copy layout feature. When you create a new project and share the configuration with an existing JSM project it will copy the request types, but after that there is no way of charing the layouts. There is a suggestion to have shared request type schemes, see JSDCLOUD-4276, which…

This can be set up using automations, there is a trigger that you can use based on when the SLA is about to breach. This is done based on if it has already breached or within specified time slots, not based on percentage.

Hi @Ben Hartley Welcome to Atlassian Community! Yes, that is possible. JSW doesn't have the approval process that JSM and JWM does (team-managed projects for now), so you would have to create the process for this. I wrote an article on how I implemented this for a Backfill project that needed all the approvers to give…

It cannot be done from within the Request form that the screenshot above is from, you need to go to Project settings > Forms in order to do this. These forms can have conditional sections that are only shown when specific values are selected from another field. Have a look at this KB for more information. Once the form has…

If you are looking for the Project summary screen then all you have to is click Summary when in the project, right under the icon and the project name.

If the options in the checkboxes are the same then you could create a custom field using the type checkboxes It would look different in the new issue view, the options will show up similar to components or multi-select fields, but when you click on the dropdown you will see the checkboxes

Hi @Tracy Reitmann, Welcome to Atlassian Community! Yes, that is possible. If you are looking for something that can be customized for each issue then you would need an app. There are multiple ones in the Marketplace that can add customized checklists to your issues. We use Issue checklist for Jira, but I would recommend…

The {{lookupObjects}} would return everything from your lookup, you still have to use the dot notion to get to the name. The first thing I would do is add a log action that you set to {{lookupObjects}}, that way you can see if the lookup is returning the object and go from there.

Hi @Russ Willis, Welcome to Atlassian Community! It can be done with automation, but on the standard plan you are limited to 1700 runs per month, see this KB. So you would either have to go to Premium or use one of the scripting apps available in the Marketplace. I have used both Scriptrunner and Power Scripts in the past…

Make sure that you have enough licenses for all the Atlassian products you are using. Adding someone as org/site admin automatically also adds them to all your Atlassian products.

Yes, you can add more fields to your request type. What you need to do is create the custom field by going to Settings > Issues > Custom fields and create it from here. If you do not know then name of the screen that your request type is using then you skip that step and just save the new field, then go to Project settings…

Hi @Ben Dossche, Welcome to Atlassian Community! Using the import functionality is a manual process, so for the initial import that would work, but if you want to do it on a regular basis I would go the REST API route unless you will be using Assets Discovery to do the import. On thing to note if you use the external…

Yes, there are smart values for Asset objects and in this case {{object.Name}} will give you the store number. Just note that this only works if you do an asset lookup, if the object is already on the issue then use the field smart value to get the name.

Try {{triggerIssue.assignee}} instead, all user fields will return the Atlassian Id when you use its smart value.

Yes, that is possible to do, and automations can span across the different flavors of Jira. I have an automation for onboarding/off-boarding tasks in our HR project that generates issues in a JWM project for one of our teams.

It looks like they might have removed that one, I just checked my sandbox and couldn't find it. But I still have it in production and this is what it looks like:

Hi @Jeff Wieland, Welcome to Atlassian Community! Under the Automation Templates tab there is one that resolves the request due to inactivity that you can use as a starting point The automation is triggered on a daily basis and uses a JQL query to get issues that have not been updated in the past 5 days or more.

Approvers can view the request when it is ready for approval, but if you want the approver to have access to the request before and after the approval is needed then they have to be added as request participants unless you are always sharing requests with the organization. 

The tables for Assets live within the JSM section, but when you set up your data connection you have the option to only select your Assets.

There is a Reports for assets dashboard template that you can start with, just make sure that your data source contains JSM projects.

You would either need to get onto the Enterprise plan so you get access to Atlassian Analytics or get one of the report apps available in the Marketplace in order to report on assets data. I am pretty sure that eazyBI can generate assets reports.

Hi @Angelo Lavarez, Welcome to Atlassian Community! The short answer is no, the default select fields cannot be based on filters. You would need an app that can get the values from an external data source like Elements Connect or any of the other apps in the Marketplace that can do this. If you are using Forms you could…

Just to add to @Arensa Prasta good answer. You also have to make sure that your other projects have a permission scheme that does not allow the client to access those. I would recommend that you use project roles in you permission scheme, that way project admins can control who have access to the project.

Screenshot of what? The workflow condition or the field configuration? If the fields are always required then the documentation I linked to should have all the information.

@Vlad Mo, No, but the tab was renamed to Templates:

The browse project permission would only work if the users have product access to Jira, and they would have to access it from within Jira. For access to the request via the portal the only option is to add them to the request participants field. So if you need the approvers to have access to the request before and after…

You would have to create a new field configuration that applies to the child issues, and in it make the fields that should only be mandatory for epics optional. If the required fields are only required as part of a transition then you would need to create a new workflow for your child issues and then remove the condition…