Mikael Sandberg Community Champion

The default one that comes with Jira is sub-task, but there is nothing that prevent you from creating a new sub task issue type called subtask and that would be my guess that an admin did.

You would need an app in order to do it. We are using Comala Document Control but there are other apps in the Marketplace that can do it too.

Currently user have to have access to your instance in order to be able to submit a form, as announced in this update from July.

Hi @James Poli, Welcome to Atlassian Community! A queue is just a filter, so to see a specific agent queue you just have to create a filter where the assignee is set to that agent, something like this: project = IT AND assignee = <agent> AND resolution = Unresolved You could also check out the reports that comes with JSM,…

Hi @Janette Kim _I_, Welcome to Atlassian Community! Yes, that is possible and is fairly easy to set up. It would look something like this: This is a simplified example, but it should get you started. 

This is what I would do, I would create if/else conditions that convert the created date to fullDate using {{[date].[dateformat]}} and then compare to see if it contains Monday, Tuesday and so forth in the if/else. And each if/else would then send the email to the specific emails. Something like this:

Hi @Jack Derrenbacker, Welcome to Atlassian Community! The organization field gets it's data from the organizations that you have created in the project. If you want to sync that with an external application you would have to use the REST API in order to do that. Your other option would be use the Help Scout to JSM app…

Hi @Matthew Butler, Welcome to Atlassian Community! Epics do not have a an epic key, it is using the same key as all other issues. So in the summary field you should use {{issue.key}} Procurement to get the result you are looking for. 

Have you or your admin turned on the global permission for anonymous access? Without that turned on it does not matter if your space allows anonymous access or not.

The only workaround would be to use an app like Structure or JXL that would allow you to create your own hierarchy. There are probably other apps in the marketplace that can do this, but these two are the ones I know about that can.

Hi @Miroslav Šestak, Welcome to Atlassian Community! The request participants field is a special JSM field that you cannot add to the request form. It's availability on the form is based on the project's customer sharing settings. On the portal the field looks like this:

It is because your lookup object AQL is too broad. You are pulling all objects in the object type, not just a single object. You would need to include an unique identifier for the object you want, which I guess in this case is the TIA Profile ID. So if you change the AQL to something like this it should work: objectType =…

Yes, that is possible. As a Jira admin you can go to Settings > System > Global permissions and from here you can change the permission for who can create team-managed projects.

Kanban boards by default do not have a backlog, you need to enable that by going into Board settings > Columns and map the status that should indicate that an issue is in the backlog.

Yes, any new issue type will by default be a "child" of an epic, unless you create your own issue type hierarchy and add the new issue type above the epic.

Hi @Julie Hiatt, Welcome to Atlassian Community! Yes, you can add a new issue type as long as you are a Jira admin for your instance. If not then you need to ask your Jira admin to do it for you. 

You have to sign up for the EAP that is currently running the Atlassian Intelligence which you can do from here. Currently the virtual agent is the only AI related feature that is in open beta.

Hi @tcampbell, Welcome to Atlassian Community! Yes, you can do this with Automation. If you go to Project settings > Automation and look at the templates there is a rule that closes the request due to inactivity that you can use as a starting point. All you have to do is change the JQL that is associated with the schedule…

So when you add a user as trusted they will automatically get access to all your Atlassian products, but they are not added to the default groups. The only way to change this is to go in to each user and change them from trusted to basic, then you can control which products they have access to.

Hi @Samantha Park, Welcome to Atlassian Community! Advanced roadmaps is part of the Premium plan, you cannot add it to tiers below it. You can see all the different features included in each tier here. 

Hi @Corey, Welcome to Atlassian Community! Yes, it is possible, but you would need an app in order to do it. There are multiple ones in the Marketplace. A couple of our engineering teams is doing this and we are using the Render Markdown app together with a script that extract the .md file in GitHub and generates pages for…

And in order to do it based on the summary field you would need an automation that looks for the specific summary, or parts of it, using smart values. You can then set the security level on the issue if the issue has the specific summary.

You need to use issue security in order to limit the access to issues that the reporter can see. Changing the permission scheme as @Divyesh Lakkad suggested will not do it. If you only give the user Browse project they will would still be able to see all issues. Take a look at this KB that describes how you set up issue…

Just to add to @Joseph Chung Yin answer, once the Forms API is released you will be able to do this, it has an endpoint that can get the answers in a flattened list. Currently the API is scheduled to be released in Q1 2024 based on the public roadmap.

Okay, since it is a custom field, go to Project settings > Fields and select Actions > Edit fields. On the next screen click on your field configuration and then lookup the field. Make sure that the renderer is set to Wiki Style Renderer. Paragraph fields will by default not be set to that, and will not recognize the…

The markdown does not have a ** option, if you want to make the text bold/strong ty using just a single *. You can find all the text formatting notation that is supported here.

Hi @Guillaume Mackowiak, Welcome to Atlassian Community! Forms currently do not have an API, so the only option right now is to link Form fields to Jira fields. Atlassian is working on releasing an API, it is currently in EAP, and is scheduled to be released in Q1 2024 based on the public roadmap. 

Go to admin.atlassian.com and click the three-dot menu to the right of JSM in the overview screen and select Manage users. That will take you to the users page and show all the users that have access to JSM. You can also go to Groups and jira-service-desk-users to remove access to JSM.

You have two options, you can either add those fields to the issue view in the request type, or add them to a Form that is added when the issue is submitted. Fields that are only on the issue view will not be seen by the customers and if you add a form as internal it will also not be visible to the customers. If you do not…

Yes, that can be done by implementing issue security and automation. The automation would set the security level when a defect is created.