Mikael Sandberg Community Champion

Since the form in Jira is associated with work item created you can trigger your automation on that and get notified when someone submit a work item. I do not think the form submission is a separate event...

Forms in JSM is different from forms in Jira. The JSM forms are based on an app that Atlassian acquired a couple of years ago, and the forms in Jira is an in house developed feature. The forms component in automation currently only applies to JSM forms.

Your JQL is missing "" around the text you want the search for, and I would do a specific search like this: summary ~ "\"{{issue.key}} - {{issue.summary}}\"" By using "\" \"" the search will only be for that phrase, not any of the words.

At my previous job we used sub-tasks for onboarding/off-boarding tasks to begin with, but then transitioned to use tasks instead because we wanted to limit who had access to the HR project and move the tasks to the projects that the different teams were using and using linked work items instead.

Hi @Maura Swart, Welcome to Atlassian Community! It all depends on what you are trying to do. If you are trying to divide the work needed between people on the same team/within the same project then yes, sub-tasks can be a good use. But then again, it all depends on what you are try do. 

A third option that I just thought of would be to use Data Manager, you could then import your data from production via the exported csv file and then use the new Data Manager import in Assets, this will also create the attributes for you.

You have a couple of options, one would be using the export function and then import the csv generated into your sandbox. Another option would be to use the REST API to either just to the import, or do both the export and the import. For the import you can use the bulk function which allows you to also create the mapping…

Yes, you should be able to do this with Power Scripts.

Hi @Jerome CLAMAGERAN (TechAndTrust), Welcome to Atlassian Community! You can contact the Billing team by going to https://support.atlassian.com/contact/#/ and from the dropdown select Billing, payments, and pricing and it will be directed to the right team.

This is a perfect example for JSM, and you can use just the regular request form for this. The use case for using Forms attached to the request type would be if you need to use conditional logic to show specific fields based on previous answers, or if you have fields that do not need to be available in Jira for reporting.…

You are correct in that you need an app for this, here is a quick search that return a couple of apps in the Marketplace that can do this. Not listed among them but I know from experience that you can do this using Scriptrunner and Power Scripts.

Hi @Viktoriya Boneva, Welcome to Atlassian Community! For any apps that you are subscribing to in production you just have to install in the sandbox and it will detect that you have a paid subscription, there is nothing special you need to do. Please have a look at this KB for more information about installing apps in…

Hi @Patrick Ramos, Welcome to Atlassian Community! On the free plan the way you add people to projects is by adding them to your instance from admin.atlassian.com. Because you are on the free plan anyone that is added to your instance will have access to all projects. If you want to limit which projects a user have access…

Paragraph fields will now by default use the Wiki style renderer so you can add clickable links in it, so the copy/paste should be a thing of the past. 

Hi @Lucas de Alcantara Pedro, Welcome to Atlassian Community! The way around this is to add a new global field that uses the Paragraph field type. 

You can check the status of the form, if it is still open for edit it means that the user just saved the form. If the status says submitted they used send.

Hi @Jeramy Furlong, Welcome to Atlassian Community! I have notified the support team that is on here and they should get back to you within 2 business days. Please note that only the core repository data can be restored, as long as the deletion happened within 7 days. Please see Does Bitbucket Cloud backup my…

Hi @McCoo, Jacquie, Welcome to Atlassian Community! What you see is expected. Forms are intended for external users outside of your immediate team. On the work item layout that you see when clicking on + Create you cannot rename standard fields like summary and description, which can be done using a form. If you want to…

Thanks @Bill Sheboy! Yes, that is what I was trying to say, but I now see that my answer missed the mark. What I was trying to say is that entity properties can only be accessed in automations via smart values or via the API and can be used to store values that should not be visible to a user.

Do you only need to use the field to store the object key or is the field used for some sort of reporting too? If the answer is no then you could consider using entity property to store the key instead. Entity properties can only be accessed via automation or REST API.

Yes, this is possible, what you need to do is change the project permission schemes for both projects so that the project that you do not want your customers to see doesn't allow them to browse to it.

Hi @Jeff Sakurai, Welcome to Atlassian Community! One way of doing this would be to have an automation that checks the amount, and then based on that either transition the work item to the status that requires the approval, or if the amount does not need approval bypass it. In you workflow you can create a transition that…

The summarize feature was a game changer for my old team when we got access to it.

Where did you change the field description, from custom fields? Note that changing the field description from the custom field view only affect new projects, in order to change if for existing projects you have to go to Project settings > Work items > Fields click on the pen icon and then change the description there.

Hi @Peter Agostino, Welcome to Atlassian Community! It depends on what you define as "manage all aspects" of JSM. Does it only include managing a specific project or the app itself? Are you using a company-managed project or team-managed one? Do you need to create new custom fields and work items? Do you only have JSM or…

Hi @Dirk Haller, Welcome to Atlassian Community! What do you mean with external projects? Is the project for collaboration with external users or are you meaning that your customer would access projects on a different instance then what the licenses are for? If the latter then the answer is no. 

You are looking at the wrong +Create. The +Create button mentioned in the documentation refers to the +Create button all the way at the top, to the right of the search bar. From here you will see the Import work items.

Hi @Sandy Yanos Welcome to Atlassian Community! There is two ways of doing this, the first thing you should look at is the request form for the request type. It will show you what the customers sees on the Portal, and from there you can also add more fields if needed. Your second option is to associate a Form with the…

The URL will give you both the JQL and the work items the filter returns. Here is an example:

Hi @Robb, Gary (G.P.), Welcome to Atlassian Community! You can use this URL to get to the filter in question: https://<your-instance>.atlassian.net/issues/?filter=<filter #>