Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
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 (...).
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!!
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
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?
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.
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.
What is going to happen during the weeklong period of potential downtime? What happens when an automation fails? We use this to track when customers get releases and it's tied to our User Creation process. Will it auto-resend any failures that occur?
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
@Justin King - We just received the email about the update taking place May 6th thru the May 13th. I do not recall getting an email about a downloadable report to be able to identify the impact. Is this available now?
Also, this was stated in the email:
• A banner will be displayed warning you that Assets is undergoing maintenance. • Automation Rules that write information to Assets will not function. • You will not be able to use imports to bring data into Assets. • You will not be able to edit or create new object schemas, object types, attributes, or objects. • REST APIs that write information into Assets will not function.
Does this mean for the entire week or just the 1 hour maintenance window?
Atlassian Team members are employees working across the company in a wide variety of roles.
April 30, 2025 edited
Hi folks!
To clarify a few things:
We don't have the downloadable report available yet but its being worked on right now. Stay tuned.
The report will only be relevant to you if there is something preventing us migrating your site. If you have received no prior email comms from us regarding this matter then assume there is no action required on your part and your migration will occur when its your sites turn.
When a migration occurs it will only take place during your maintenance window and only in the week that we have specified in the email you have received (if you have not received one, don't worry, we are working through everyone group by group. This may take a little time).
The downtime will occur once (not multiple times throughout the week). So for example if we specified the week beginning 1st of May, then on a single day during that week, you will experience a short downtime in your maintenance window.
For most sites this downtime will be very short (minutes). We mention that it could take 1 hour only to cover exceptional circumstances.
Read operations will continue to work in Assets during the downtime. It is only write operations that will be paused.
I hope this helps and if anything is still unclear please let me know!
1). We initially misinterpreted the email communication as "Jira Assets will become read-only for 8 days", due to phrasing present in announcement email: "During the maintenance period, no writes can happen to the Assets database." :D Your clarification above makes it fairly clear this isn't the case - and that the entire additional downtime related to this will be limited to (up to) 1 hour, but correct me if I'm wrong, of course. :)
2). Assuming the above is correct... I understand that you cannot predict in advance the precise date/time when each instance is taken care of. However, will there be any email communication sent (on a per-instance basis, just like with the last week's announcement) once the downtime has finished, so we're aware that there will be no more potential disruptions?
I have a follow-up question regarding the planned maintenance for Assets in Jira Service Management scheduled from May 15, 2025, to May 22, 2025.
Could you please confirm if all the backlog of automation rules that won't function during the maintenance window will be re-executed once the maintenance is complete?
Atlassian Team members are employees working across the company in a wide variety of roles.
May 12, 2025 edited
Hi @Gunjan Ahuja. I'm sorry but we don't have the ability to re-execute any automation rules that will have written to Assets during the maintenance period.
Hey @Chisato Saito. Unfortunately until a site aligns with the limits we have introduced such as max 120 attributes per object type we are unable to ship improvements and new features for Assets to that site. This is because it wont be compatible with the new system architecture we are rolling out.
I just received an email today about taking action and the email indicated that we were recently emailed about this. We have until June 13, 2025 and this was the first email we received. So needless to say, we are kind of scrambling to figure out if and how we are effected.
Its possible you were one of the few customers who only began breaching one of these limits between the original mail out and yesterdays mail out. Sorry for the surprise. The email will contain links to downloadable reports which will tell you exactly where any changes need to be made.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
I have checked and your site no longer looks to be breaching any limits. You may have been breaching one of them at the time when we sent the original email and since then your data has changed.
51 comments