The communication was not clear (not everybody understands what "unique constraints" means)
The implementation timeframe seemed too aggressive (two weeks isn't enough time for everyone)
The instructions were lacking actionable insights (now we know we have a problem but where do we need to go to fix it?)
As admins, we need better ways to identify and address any asset configurations that exceed platform limitations
There are some use cases that require more than two unique constraints
Recommendations for Customers
As many have pointed out above, Atlassian Support generally assists in situations like this and can help point you in the right direction. @Pier-Olivier Tremblay has an interesting solution if you'd like to roll up your sleeves and dig in without engaging the Support team.
Recommendations for Atlassian
Better communicate (including the why and if this is a temporary or long-term limitation), provide tools or examples to help admins when their action is needed, and provide alternatives or exceptions for situations where the proposed constraints are too limiting.
Now Time for a Deep Breath
These outlined critiques are valid. That said, I've been following the work of the Assets team over the past few quarters and have personally spoken with @Justin King about specific concerns and requirements. To their credit- they are doing a lot of work behind the scenes to make the assets platform more performant, reliable, and scalable. Our company has noticed improvements in those areas and are looking forward to the upcoming features on the Assets roadmap. There are some Atlassian decisions that would warrant an angry mob with pitch forks; this one just doesn't appear to have risen to that level yet...
This might sound like more piling on, but the assets backend really does need some performance enhancements. I can see that and for sure support the dev work on improving it. Eager to see it come to fruition, and I'll be most grateful if so. The system has already proved useful enough to be quite integral to our day-to-day operations, so I offer my existing gratitude there - thanks!
Cloud services hold customers hostage to their inner workings in a way that offline offerings do not, which is a fact of life that customers ostensibly accept when agreeing to use them. In exchange, a customer receives benefits from new development efforts and offloads the tasks of maintenance and support. If a customer should find that that arrangement no longer meets their needs, the free market can work its magic.
As such, my main polite asks here are for more communication as outlined by Josh, including a mention of legacy support for (or at least what happens to) customers who may not be able to comply on this timeline. Here's hoping that lessons get learned, and the end product improves.
Atlassian Team members are employees working across the company in a wide variety of roles.
March 11, 2025 edited
Hi everyone.
I apologise if this has caught you off-guard. I agree we should have sent the reminder email sooner.
On the issue if locating your attributes that currently have unique constraints. Thanks for the feedback, I can see how in some cases this could be challenging. We are evaluating how we can help with this and I'll post an update on that soon.
30 comments