Reminder - Changes coming into effect in Assets for Jira Service Management

[Milad S_]

Hi @Justin King

Thanks for the update.

I was just wondering whether you would consider a feature where system provides warning/error when a user want to breach these limits.

Like others, we received the email notification. While we worked out the object type causing the issue, I found out that we can still exceed these limits without warning or error. For example, I tried a couple of days ago, and it was still possible to add unique constraints to more than 2 attributes. 

It is quite easy to unknowingly breach these limits given the setting (for some of these limits) are behind the 3-dots (...).

[Shankar Rishikesh]

Hello Atlassian,

It is really strange that you remove features which were used for long and ask us to adjust it as per your changes, why do you do so? If someone is using it for longer time, it is a task to do so without any reason, who will pay for the task to undo things or adjust the workflows or something ! do you expect everyone to engage resources for the task!

I am not happy the way Atlassian keep updating Jira every now & then...please stop doing so, it does not help us. Instead, improve Jira and give some features which is more important like Sandbox copying assets, importing from AWS assets, attachments from opsgenie to JSM, automation trigger order etc...

for example, recently, you merged Opsgenie but did not give user access properly, now without giving them browse access, we cannot add users in Teams (earlier it was not required), also giving them admin access is a problem...

I would request you to spend time on important and meaningful feature even if there is only one vote count, rather than doing some cosmetic changes which are really not required! also, at the end, Do not remove features which are being used for more than months!!

Thanks,

Shankar

[Daniel Vest]

Does anyone know if this "changing of the AQL & dot notation" will adversely affect automations that use the . attribute references? If so, that will be quite unpleasant! We have several automations that will reference items in the Asset area, looking up information (example User Jira.accountId) then using that information to edit fields in tickets, or many other things, even when using forms/tickets to edit the asset's information. Does this also impact areas where a lookupObject is done in an automation and then you are able to reference all the attributes of that object ( {{lookupObjects.Email}} ) and use it later in the automation?
Your thoughts, @Justin King

[Majken Longlade]

What is the workaround when more than 2 attributes should be unique? If you have a people schema, email, employee ID, phone number should all be unique. For hardware, serial, service tag, MAC address should all be unique. What's the recommended way to check for duplicates?

[Justin King]

Hi @Daniel Vest

That change has no effect anywhere except for usage in import mapping so your automation rules will be fine!

[ankur.patel]

UC will no longer be supported on TextArea attributes.

I am not sure how to achieve this without having unique constraint for the TextArea attributes. What happens to the attributes like serial numbers?

Does that mean we have to consider the risk of duplication? 

With these new limits, JIRA Asset module is unusable. 

Can someone please clarify this if I have not understood correctly?

Thanks 

[Justin King]

Hi @ankur_patel

Could you elaborate on your use case for UC on a TextArea? 

Thanks!

[ankur.patel]

Hi @Justin King  I meant to say Unique Constraint as it was not letting me post my comment. 

[Heather Weatherholt]

I hadn't even thought about the issue @ankur_patel raised.  We will have the same issue for most of our fields, and we would want to make sure there are no duplicate tag numbers, asset names, serial numbers, MAC addresses, IP addresses, etc.  I agree that it will become pretty much unusable, or we would need one person whose sole job is to constantly check and correct our assets to ensure there are no duplicates.

[Chris Troyer]

@ankur_patel @Heather Weatherholt 

It sounds like Unique Constraints will no longer be supported on TextArea, but I imagine they are still available for Text fields, which is likely the attribute type value for the fields you referenced. We are using the Assets Discovery tool, and it created Name, Hostname, FQDN, Serial Number, and MAC address all as Text fields. IP address is its own unique attribute type value.