Linked Trello cards no longer displayed on Jira tickets

[frabinstein]

There used to be a section on Jira tickets displaying all Trello cards that linked to it.
This section is now gone.

This is an essential part of our workflow.
From a Jira ticket, we need to be able to see which Trello cards are linked to it.

Having lost this functionality is very disruptive for us.

[Trudy Claspill · Accepted solution]

Hello @frabinstein 

Have you checked with your Jira administrators to see if they disabled that functionality?

I don't use Trello, but when I used Google to search on this topic it returned this information:

1. Install the Trello Power-Up 

• In Jira, you must first install the Jira Power-Up for Trello to enable the integration.
• This will allow you to connect to your Trello boards and link to cards directly from Jira. 

2. Link Jira issues to Trello cards

• Open a Jira work item and find the option to link a work item. You can then select and link to an existing Trello card.
• The link should automatically be created on the Trello card, so that both Jira and Trello users can see the connection. 

3. View the linked Trello items in Jira 

• In the detail view: By default, linked Trello items will appear in the detail view of the Jira work item.
• On the board view: To see linked items directly on the board, go to the "View settings" (usually in the top right corner) and enable the toggle for "Linked work items". This will display a link or icon on the relevant Jira cards, indicating the connection to Trello. 

[frabinstein]

This is resolved now.
Thank you for your answer.

I'm still not sure what the problem was, but it must have been something on my side; not Atlassian's.

• My Jira Admin assured me nothing had been disabled or changed from a few days before, when the functionality was working for me.
• Then two days later, I just refreshed the Jira ticket page once more, and the Trello section is back.

This might have been just a cache or browser memory issue, although I had of course tried rebooting my machine before, and the issue was still happening.