Mikael Sandberg Community Champion

The short answer is no, your main project cannot see the Story point estimate from a team-managed project. TMPs do support some global fields that are company managed, but Story points is not one of them. So currently your options would be to convert your TMP to a company-managed one in order to see story points on the…

Hi @Lisa Gray, Welcome to Atlassian Community! What information are you trying to save and to what? If you add a screenshot of what you are seeing that would make it easier for the community to help you solve the issue.

Odd, it should follow the normal text formatting notation. Have you tried any of the other notations to see if they work, like the one of the text effects or headings?

Hi @Dakota Alverson, Welcome to Atlassian Community! You do not have to add any special line break characters in the Portal introduction text, just treat the field as a normal multi-line text field. Here is an example of our looks like: And this is what it looks like on the Portal

Hi @Vishnu Priya Thummala , Welcome to Atlassian Community! Is the workflow used in that project shared with another project? If not and if you have Jira admin permissions you can modify the workflow in question without affecting other projects, just be aware that you should never rename a status since they could be used…

Hey @Tomas Fernandez, not sure if you have seen the latest What's New in Jira Service Management but you are now able to restrict request type to specific users and groups. 

@Monica Your rule would basically just have multiple if/else conditions in it. Here is an example from the rule I have for application access: In this case as you can see if the application = DemoPro or Crayon, the request is moved directly to Approved and will therefor bypass both Manager approval and system owner…

@Alyssa Hill The second rule would trigger on transition as pictured above and because you are using the parent branch it would only run if the issue that is transitioning is a subtask and then you use the parent branch to transition it to the next status.

Since the automation is a scheduled one the trigger issue will not work. You would have to break the branch part out to its own automation for it to work. The automation would trigger on issue create and then you can use everything from If: Issue matches JQL and down.

You would need at least two automations. The first one would be on issue create which adds the subtasks that you want. The second would be on issue transition that moves the parent issue to the next status and would look similar to this automation template:

Hi! Are there any plans on supporting Assets object fields? Our use case is that we sync teams from an external application and would like to be able to associate an idea with a team.

You could use automation to copy any comments from the side ticket into the main one if needed, but if you link them then it might be easier to just go to the side ticket to see any comments.

Hi @Pavithra Kandula, Welcome to Atlassian Community! You can find the API documentation for Forms here, https://developer.atlassian.com/cloud/forms/rest/intro/ 

You would have to create multiple automations in order for this to work. The way your rule is currently configured it is expecting that the issue that triggered the automation is in the the closed status and it has a parent. Your first rule should be in issue create and that will add the forms and the subtasks. The second…

Hi @Steeve P_, Welcome to Atlassian Community! JSM do not have the "side conversation" that would allow you to include external users with no access to your instance. Internal notes can be used for internal conversations that is not visible to the customer, and you can set it up so developers can go in and add their…

Yes that is correct. And if you have fields with the same name or if the automation says that it cannot find the field then you can use the custom field Id instead. You can get that Id if you go to Settings > Issues > Custom fields, locate the field in question, then click on the three-dot menu and hover over one of the…

Hi @Andy T, Welcome to Atlassian Community! In order to include the fields in the body of the email just add them like this: {{issue.first name}} {{issue.last name}} {{issue.date}} {{issue.title}} In order to include answers from a form you would have to use the Forms API in order to extract those answers. You can find the…

Hi @Alexandra Ridgway, Welcome to Atlassian Community! Team-managed projects have only access to a limited amount of reports, in order to get the reports for issue analysis you have to use company-managed projects. 

You can find the Forms API here, https://developer.atlassian.com/cloud/forms/

Queues are basically just filters, so in order to route ticket to the right queue based on form answers you would either need to link the field to a Jira field. The other option would be to use the API for Forms to get the answer and then either set a component or a label and this will route the ticket to the queue.

From the Configuration page, click on Edit the layout of your help center: Another way to get there is to go to your project and click Channels > Portal and then navigate back to the main help center screen, from here click Customize and you will see Edit homepage layout.

Instead of selecting Customize, go back and select Edit home page layout. From here you can select the projects that should appear under featured, and you can also hide projects if needed. Once you are done editing, select Publish layout at the top.

If you are using the new workflow editor you would see something like this when you click on the condition: If you are using the old editor you will have to go to Conditions in order to see this:

Yes, that is possible. All you have to do set the channel access to restricted, and then add a group that includes all the people in the company as service desk customer under people.

Because the automation I included above is a scheduled one you can set it to run whenever, once you saved it you have the option to run it right away and after that you can disable it unless you want to run it on a schedule.

@Theresa The automation to set the resolution on issues that are already closed/done would look like this: The one @Kelly Arrey included above would only work on issues that are currently not in a closed/done status, and in that case it is better to use a post function in the workflow instead of using an automation,…

If you change the permission for browse project to look something like this then your customers will not be able to use the create button even if they have access to Jira. The draw back is that you will not be able to @ mention customers/users that are not either the reporter or a watcher/request participant on the…

It all depends on what header Boomi is expecting. For example Jira is using the Authorization as the header and then you add the email address and API key as the value, something like this: The API reference should have all the information that you need to set up the authentication header.

Hi @Matt Grayford, Welcome to Atlassian Community! One way of doing it would be to use an iPaaS like tray.io, workato or any of the other ones out there. They are low code/no code ways of interact with different APIs and integrations. I use tray.io for multiple things, like getting assets from Intune and Jamf into Assets,…

Hi @Anna Oaks Welcome to Atlassian Community! You can do this by adding Dashcards to your column, they will show count of cards in the column and can also alert you when a card is moved into/out of the column.