Caroline Bartle Atlassian Team

@Rick Westbrock The affected services field will allow you to select all services types.

@Masayuki Abe There will be no change to the behaviour of the Affected Services field, nor the Change Calendar as a result of the change described in this update.

Hi @Hayden Young - deleting them in JSM will indeed persist a deletion to Compass as well. I'm interested in your use case, and I wonder if you could share a bit more about your scenario, specifically: Services list in JSM is supposed to be a list of environments for our applications Are your environments set up as…

I forgot to add - we'll be updating our documentation to reflect this new addition. Apologies for the delay on this. 

Hi @Rick Westbrock - we've rolled out service types to Services in Jira Service Management as the first step towards supporting a sync with Compass. Compass supports a number of components, a subset of which we know are critical for customers using Jira Service Management for IT Operations (in particular, for incident and…

@Dave LIAO @Antreas Solou we don't have plans to bring this update across to Assets in Data Center (given Jira DC supports slightly different UI patterns). Are there specific aspects to this UI update in Assets Cloud that you'd like to see in DC?

Hi everyone - a few updates to make on the new UI for Assets: * The last view (i.e. list vs detail) is now remembered (cc @Cosmo Denger, @Richard Amery, @Ariel Kauan * Reference depth in the object graph is working again (cc @Heikko E) * There have been a number of comments about search no longer functioning the way that…

Hi @Sue Lund - we've resolved the issue of users and groups not displaying in list view (https://jira.atlassian.com/browse/JSDCLOUD-12528). You mentioned that you're having problems tabbing through attributes. This capability is still supported in the new inline editing view - could you please share a bit more about the…

@Majken Longlade we're working on the bug related to searching by attributes (https://jira.atlassian.com/browse/JSDCLOUD-12509) so hopefully will have that resolved soon. Can you please tell me a bit more about the problem you're encountering with not being able to search/filter against abstract object types?

Thank you for bringing this to my attention @Sue Lund. Yes, we will be fixing this. 

Hi @Eric Krueger _StrataCom_ Inc_ , I'm afraid that isn't part of this release. Could I ask for a bit more information as to why you'd like to see the two APIs combined? Are you blocked from performing a particular task with them being separate?

@Larry Brock _Praecipio_ I have included that tag, but I'm afraid this update is just for cloud. I'll make some updates to the article to ensure that's more clear. Apologies for the confusion!

Hi everyone - just an update that we have now shipped the QR code feature to Insight as part of Jira Service Management. Documentation related to the feature can be found here: https://support.atlassian.com/jira-service-management-cloud/docs/print-qr-codes/

Hi @g_delarosa - just an update that we have now shipped the QR code feature to Insight as part of Jira Service Management. Documentation related to the feature can be found here: https://support.atlassian.com/jira-service-management-cloud/docs/print-qr-codes/

Hi @Josh Martin, sorry for the delayed response. You can migrate existing JSM portal-only customers to Atlassian Account via Atlassian Admin > User Management > Jira Service Management, and then clicking "Migrate to Atlassian Account" on the triple dot menu of a user. There's a bit more info about portal-only customers and…

Thank you @Ross McCardal and @Josh Martin for your responses. I've been looking into this further - I believe that the documentation page shared is inaccurate (we'll have it updated). Portal users don't have to be licensed for Jira to see the Affected Services field, however they do have to have an Atlassian Account to see…

Hi Josh - The Affected Services field isn't agent-only, and should allow your customers to select a service (whether it's set to mandatory or not) when the field is included in your request forms. Are you able to provide a bit more info on the errors you're encountering? 

The Create Linked Issue feature is most frequently used by support teams (in JSM) or business teams (in Jira Core) to raise bugs, improvements etc in the backlogs of software teams. Hence why it exists in those two products / project types. I'm afraid that there are no plans to release it to Jira Software anytime soon.

I'm afraid not @Matias - this functionality is only available in Service Management and Business projects.

Ah ok, apologies for that. I'd suggest raising a support ticket for this: https://support.atlassian.com/contact/#/

@Matthew Faust the option to "link issue" is in the main part of the button in the screenshot you shared:

Hi @Al - that's really unexpected. The permission for creating linked issues is tied to the "linked issues" permission so the fact that you can see the linked issues module means that you have that permission. That applies to both Jira Service Management and Jira Core (not JSW, where this feature doesn't exist). I'm sorry,…

@Yann JOUAN You can create a linked issue Jira Service Management and Jira Core projects in the new issue view. To do this, click on "Link issue": Then under the "linked issues" module, you'll see the option to "Create linked issue":

Hi @Jeffrey Bistrong - issue layout in Jira Service Desk is managed at a Request Type level (as opposed to an issue type layer in Jira Core and Jira Software). You can access this by navigating to Project settings > Request Types and then clicking on Edit Fields of any given request type.

Hi Trudy, The location and display of the request channel has changed in the new issue view. This information is now available as part of the request details panel (alongside the name of the customer who raised the request):

Hi Carrie - I've been trying to nail down the bug you're encountering with transitions in the new issue view, but haven't been able to reproduce it. I'm able to see looped transitions that are set up with a condition to display to users in a particular group within the new issue view. But maybe there's some variance I'm…

Hi @Dan McClintock - we're very close to rolling out the new issue view to more Jira Service Desk customers (i.e. in the coming weeks) If you want to have it switched on for your instance, you can raise a ticket with our support team to have them do this for you.

The "create sub-tasks" buttons are now available in the new issue view for Jira Service Desk. You'll find them in the quick actions section (below the summary) and also in the sub-tasks component: https://jira.atlassian.com/browse/JRACLOUD-72135

Create Linked Issue is now available in the new issue view of Jira Service Desk. It can be accessed as a link via the "Link issue" button and component:

Create Linked Issue is now available in the new issue view of Jira Service Desk. It can be accessed as a link via the "Link issue" button and component: