Horrible decision, this power-up is an integral part of our everyday work in the product team to plan and monitor roadmaps and projects against Jira progress.
The replacement won't fulfill the current capabilities of the power-up as many of the comments here point out.
Such a step can make us start looking for alternatives and we really like Trello :/
I have to concur with literally everyone else here.. this is a mistake that really should be reconsidered.
Trello automation is not a substitute for this. Currently, from a Trello board our team can raise an issue in Jira, including choosing the project and issue type. Automation doesn't allow for that as far as I can see. Being able to specify the basic details of a Jira ticket from Trello is why we use this.... a client-reported issue could be a bug, and enhancement, a feature request, etc.
It seems that we now are going to have to go back to creating the Jira ticket manually, just so we can get that right and then pasting the link back into the Trello card... that's a huge retrograde step.
Reading the article and all the comments, I cannot even fathom the reasoning for removing this power-up. You are adding 'Smart-links' which only does like 1/3 of what the power-up provides and the article writes it in a way that we are rewarded with a cool new feature, something to look forward too...
Yes, the smart-link shows the jira issue in a nice way inside a text field. You can see the progress etc. But where is the link in jira to said trello issue? The power-up does this, smart-link fails to do so. There's no 2-way link anymore. Yes, this can be done by hand in Jira but why should we if a working power-up already does this for us?!
This is crucial for us. Trello is being used for the managers and planners to discuss with other departments on what to do. From there the link is established with jira so the developers can work from there.
Creating an issue from trello to Jira. This feature works perfectly, why remove it without offering even the slightest thing as a replacement (trello automation is not a replacement for a working and functioning power-up).
We've chosen to use trello specifically at the beginning of this year to stay within the atlassian ecosystem because everything is easily interconnected and making things easy to find from 1 application to another without having to program/automate everything ourselves. We are a rather small company and we do not have the time (or money) to be constantly busy with automations within trello and jira to create the simplest of functions for ourselves (this should be within the application). We need to be busy with our actual work and not be busy with applications we use in order to do our work.
I hope atlassian reads all these comments and will consider at least pushing back the deprecation date, wait untill all the features from the jira power-up are replaced within trello or even better, integrate the look and feel from the smart-link with the power-up. Best of both worlds in my opinion because I do like the look and feel from the smart-link, also with the full screen view option but it lacks important features compared to the jira power-up.
Hopefully the atlassian team does something with this because having an article being viewed over 5000 times, having only 5 likes but does have 27 comments with all the same reply "please keep the power-up" shows that people are not in agreement with this idea. And with people I mean customers, paying customers.
Reading all those comments I understand something - A lot of Jira users are using Trello to solve a problem Jira should solve - just add that option in Jira and catch two stones in the same stone.
I use the Confluence power up and if there are todo items, they are added to Trello automatically as a checklist, which doesn't happen with your new approach.
This new 'smartlink' feels more lobotomised than smart, and removes functionality.
+1 on the UI changes beeing less functional. Currently with the smart card, it looks nice when you open the card, but i am missing the status we see when on the Board view on the card showing me that a Jira card is linked.
Omitting this would be a step back in my opinion. We use this in the overview to quickly check whether trello cards have a Jira card linked. To do this i would not like to click on each card individually.
+1 also on the 2-way link. We utilize the connection between the cards aswell. With that gone, it becomes a hassle.
@tal.sela we start out in Trello (as lets say a question) and from there move to jira (the actual development task), what do you mean with a problem that Jira needs to solve? Im genuinely curious to what you mean, because maybe im thinking about it the wrong way :)
I was wondering if any of our comments have impacted the decision to move forward with this change. Alternatively, is there a possibility for you to continue supporting the feature that we all use and love?
@Jan van Luijn I fear it won't, I suspect this decision is all wrapped up (I'd love to be proven wrong).
It really just feels like they don't want to support the power-up and hence it will die. The fact that Smart Links and Trello Automation are being pushed as an alternative would suggest that the people who have made this decision don't really understand the use-cases well enough.
That Trello Automation has been around since April 2020, and lots of us are still using this power-up extensively should tell you something!
The current rationale seems to be, "We have these whizzy new things for you, so we're getting rid of the really useful old ones you use." And that would be fine, if it didn't represent a huge loss of functionality.
I'm rambling now, but mostly because I'm grumpy about this! It's going to screw up our workflow a lot, and we're now actively looking at other platforms.
@Ellie Kulick and Atlassian. This is a core functionality and frankly the only reason we use Trello so we can show to clients the status of development tickets. If it is not matched in kind, we will likely be moving our business elsewhere -- everything Jira, Confluence etc....and the thousands of dollars we spend annually.
This is a horrible Idea! I have several Power Automate tasks that create a new Trello card each time a Jira ticket with specific parameters is created. Now instead of SmartLink the in ticket, it is just adding it as a linked attachment.
The new inability to see the ticket's progress from my board is not good. Also, when opening the ticket and it's not SmartLinking, I have to open the card and then open the link to the Jira ticket to get any context on what is happening. It was much easier to have an overview of the cards/tickets that are open.
Smart links are very interesting to visualize JIRA issues from Trello, but logging an issue in JIRA could be more flexible when working with multiple projects in JIRA.
But I also don't understand the reasons behind the decision to change the power-up.
How does one keep a view of multiple JIRA tickets in a single Trello card? We work with two different Development teams through JIRA but have one Trello board. It allows us to keep all JIRA tickets for a project on a single card but be able to see who is assigned to the web development parts and who is assigned to the email/social part by using this Power-up. PLEASE do not make this more difficult, especially as we are heading into the back half of the year. Having this power-up in an eCommerce business is crucial to our success with staying nimble in Q4. We create our JIRA tickets from Trello and it allows our content team to do most of the upfront setup within Trello where our briefs and other content lives.
This decision an action seem very much in line with other actions in the Atlassian ecosystem, where existing working functionality is sacrificed in favor of some nebulous goal that the users cannot see in front of them and frankly never see an improved alternative.
I've been using Trello for around a decade. I've used it to introduce several businesses to better programming process management as opposed to the adhoc way they were doing it.
Our current shop uses Jira but it has so many obstacles to viewing flow that we started using Trello (after I introduced it once again and pointed out that it was in the ecosystem) as a core part of process so an individual application project could be viewed in a single page to show where things were, a visual scrum in some ways. One of the crucial parts of that was adding cards in Trello, fleshing out the descriptions and details and using that this power up to create the jira ticket for company event tracking so on. WE would then use the power up to tie in any other associated jira tickets so we had a single place to see the relations.
Micheal Heikka, @Ellie Kulick - You've removed a core piece if functionality again. All these users here are telling you we need the functionality. Jira had a lot of love 5-7 years ago in the agile community. Now it is talked about in the same way some places discuss formerly loved tools that have been acquired by Oracle.
Thing is that I may not have a voice in the decision making process where I currently am in terms of project management tools, but I have in the past and I will again in the future. And I can assure you, due to things like this, I will not be suggesting anything from Atlassian to the table and will actively resist using it.
p.s. Micheal Heikka does not appear to be linkable anymore... interesting.
I use the powerups to quickly glance at status of the jira case and to see which one of my cards have jira cases created, and which ones are missing cases. How can I do this at a glance with the new smartlink feature without having to open the card itself? This feels like a step backwards.
Atlassian Team members are employees working across the company in a wide variety of roles.
July 28, 2023 edited
Hey everyone! Thank you for all of your feedback. It's so great to hear that the Jira and Confluence Power-ups have been serving you all well.
I'm very happy to share that we've heard you, and both the Jira and Confluence Power-ups are here to stay! They have been restored on the marketplace and we no longer have plans to deprecate either of the power-ups.
Thanks again for sharing your feedback. We appreciate you!
Well, credit where it's due. I've just seen the update, and I'm pleased that the power ups will remain. Thanks Atlassian.. I hope that it's clear the user-base are happy to engage with you on this kind of stuff, and value the products. I'm sure plenty of us would be happy to offer information during the consultation / planning process for these decisions to help avoid all the stress.
Thanks, Atlassian for listening to us users and considering what we say! We have nothing against new features as long as they don't remove the features we need and make use of!
@Ellie Kulick Just wanted to make sure to drop a very heartfelt Thank You from our team for this decision! We're very happy overall with both Jira and Trello and are looking forward to continued partnership.
49 comments