Mikael Sandberg

How are you creating the 6 new tickets? Via automation? You can set the summary as part of the automation, you just set the summary field to be {{issue.summary}} - Research the reason.

in Add the summary of a linked issue to the summary of the linked issue. Comment by Mikael Sandberg February 2023

You should be able to do that using automation and HubSpot's REST API. I took a quick look at HubSpot's API and you would need to know the companyID in order to get data regarding it.

in Populating Custom Fields on Support Tickets Comment by Mikael Sandberg February 2023

Currently the only option would be to link each field in the form to a Jira field so that it shows up in the request without having to open the form. Once the REST API is released you could get the information that way and just add it to the description field. Currently the API is scheduled for Q1-Q2 2023 according to the…

in How to Get ALL Form Fields to Show by Default in Service Desk Tickets Comment by Mikael Sandberg February 2023

Hi @T, Welcome to Atlassian Community! No, you would need an app for that, I did a quick search in the Marketplace and it looks like Awesome Graphs might be able to do it. Back in the days when I used Bitbucket Server I created my own web app that generated a report will all pull requests related to a release.

in In Bitbucket is there a way to obtain a list of all pull requests from one story? Comment by Mikael Sandberg February 2023

Yes, analytics should be available for you if you are using Data Center and have enabled it. See this KB for more information.

in Is the Analytics feature available for the on-prem version 7.18 Comment by Mikael Sandberg February 2023

Hi @dkwan Welcome to Atlassian Community! Yes, this can be done using automation. You would trigger the automation on issue created and then use if/else condition to assign the issue based on the value in the select field.

in Is there a way to map a form to a specific assignee Comment by Mikael Sandberg February 2023

Yes, if you go to Settings > Issues > Workflows and once you located the workflow you want to copy just click on the three-dot menu on the right and you should see Copy as an option.

in Can I copy a workflow? Comment by Mikael Sandberg February 2023

Hi @Jordan Cox, Welcome to Atlassian Community! The feature you are looking for is Clone. So after you created the first asset, go into it and click on more and you will see Clone. If you have a lot of these clones that you need to create another option would be to use the import feature. You learn more about it here.

in Creating Multiple Assets of the Same Type Comment by Mikael Sandberg January 2023

You will not be able to do it from the board, unless you first move it to a different column and then back to the done column and select a different status. But you can do it either by going into each issue and change the status, or create a filter will all the issues that you want to move from "Ready for Prod" to Done and…

in Assign multiple columns to done status Comment by Mikael Sandberg January 2023

You would have to do it in two steps, you cannot set additional field values as part of the move process. After the issue has been moved just go into it and set the epic link. Your other option is to add the epic link to the screen in the JSM project, set the value of the epic link and then move the issue over.

in I would like to move tasks from Service Desk to an existing Epic in a JIRA software project Comment by Mikael Sandberg January 2023

A status can only belong to one column on the board, but you can have multiple statuses assigned to the same column.

in Assign multiple columns to done status Comment by Mikael Sandberg January 2023

currentUser() is case sensitive, so try this query: "Request participants" = currentUser() OR watcher = currentUser() OR assignee = currentUser()

in How to list all the issues on which I am a participant, watcher, the assigned person. Comment by Mikael Sandberg January 2023

No, the project key can only contain alphanumeric characters, so then-ADMIN would not work.

in How to create specific Ticket Comment by Mikael Sandberg January 2023

It is not possible, Jira will pick the next available number and there is no way of controlling that. Instead of cloning the issues what you could do is move them to the new project, that way Jira will forward users to the new project if they have a link to the old one. For example, in my old project I have JRA-123 which I…

in Possibility of Keeping Issue Keys the Same When Cloning to a New Project? Comment by Mikael Sandberg January 2023

Hi @Andre Rodrigues, Welcome to Atlassian Community! The automation to set the end date when transition to done is a simple one and would look like this: In this example I'm using due date because I don't have a custom field for end date.

in Auto populate end date when status done Comment by Mikael Sandberg January 2023

Components allows you to organize your issues in subsections within the project, for example you could have components for services or APIs. Labels can be used in a similar way, just note that you cannot control labels the way you can control components. For example you could have a label named JIra, and another named…

in How to create specific Ticket Comment by Mikael Sandberg January 2023

Have a look at this KB. The level number following the default setup in Jira Software where Epics are level one, stories/tasks are level 0 and subtasks are level -1. See it as showing the number of steps away from epics the new level is.

in How to set a hierarchy with three levels below epic Comment by Mikael Sandberg January 2023

The issue key cannot be configured that way, Jira will pick the next available number, and you cannot reset that unless the project is deleted. The only part that can be changed is the project key before the numbers. What you could do is add a component or label to these time tracking tickets, that way you can filter on…

in How to create specific Ticket Comment by Mikael Sandberg January 2023

Hi @jeffhardy networth, Welcome to Atlassian Community! Currently it is not possible to move objects between object types. Have a look at this question that is the same as yours, https://community.atlassian.com/t5/Jira-Service-Management/Moving-Asset-Objects-to-Object-Type/qaq-p/2255880

in Changing the Object Type of Asset Objects Comment by Mikael Sandberg January 2023

Hi @Joseph McCarron, Welcome to Atlassian Community! Currently it is not possible to create more queue groups, but you can always suggest it if you go to https://jira.atlassian.com/ and provide feedback.

in Create more than 2 Queue Groups (Currently Team Priorities and Other) Comment by Mikael Sandberg January 2023

That refers to the "Invite To Edit" feature in Confluence Cloud: It has been a while since I used Confluence Server so can't remember if this feature is available there.

in Cannot share draft Comment by Mikael Sandberg January 2023

Currently it is not possible to move objects between object types. I did a quick search in JAC and could only find a suggestion for Jira Server to add a feature that would allow you to do that, JSDSERVER-10940. I would suggest that you add one for JSM Cloud if you want see that added there as well.

in Moving Asset Objects to Object Type Comment by Mikael Sandberg January 2023

Hi @[deleted], Welcome to Atlassian Community! The request form is what the customer sees in the portal, and the issue view is what the agent sees when accessing the request in the queue. The request form can rename the fields to make it more clearer to the customer what information you are looking for. Example, you can…

in What is the difference between Request form and Issue view in the config menu of request types? Comment by Mikael Sandberg January 2023

Hi @María Isabel Marroquín, Welcome to Atlassian Community! Drafts don't have the share button, so if you want to share it you have to copy the URL and share that. You can only use the share button within Confluence one a page has been published.

in Cannot share draft Comment by Mikael Sandberg January 2023

The Change type is a custom field that you can add to. Just go Settings > Issues > Custom fields and look up Change type. Then click on the three dot menu on the right and select Contexts and default value.

in how to add an additional change type option? Comment by Mikael Sandberg January 2023

Hi @Vinodh Sirikonda, Welcome to Atlassian Community! You can do this by using the Jira issues macro it allows you to show a list of issues based on a filter.

in Insert Jira ticket, its description and status in Confluence Comment by Mikael Sandberg January 2023

Hi @Rantly Liriano, Welcome to Atlassian Community! Yes, that is possible. Just go to Project settings > Request types and select the Changes work category. From here you can add move change request types.

in how to add an additional change type option? Comment by Mikael Sandberg January 2023

Yes, like lookup issues, lookup object is only returning up to the first 100 objects that is searched.

in Is lookupObjects capped at 100?? Comment by Mikael Sandberg January 2023

In its simplicity the rule would look like this: If you are not using whole numbers as story points you would have to encounter for that and add Round to the smart value, else you would get an error when changing the due date.

in Automate "Target Date" field when ticket is moved to "In Progress" AND has Story Points populated. Comment by Mikael Sandberg January 2023

No, you do not need Jira Service Management to create issues and comments via email. The KB that you found outlines the steps how to do it in Jira Software. It is mentioning JSM as a solution if you are looking for a help desk solution, which also have an option to create issues via email.

in Will implementing the email to ticket solution require a separate license? Comment by Mikael Sandberg January 2023

Mikael Sandberg Community Champion

Comments