Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Edit Jira values from database or database/entry macro

Sigrid H August 9, 2023

Hi, I love the database functionality that allows me to embed specific values if a Jira issue for a database entry while having other values that are managed in Confluence. This for us closes parts of a huge gap in the way Confluence and Jira work together. We will save a lot of time and effort in managing our content.

That being said, what would increase the value of this even more is if there was a way to edit Jira values from the database or macro. Inline in the table would be great, but it would already help if there was the option to open the Jira issue on the Confluence page e.g. in an overlay. Are there any plans to introduce something like this?

Thank you very much!

1 answer

Suggest an answer

Log in or Sign up to answer
0 votes
Divya Sriram
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 1, 2023

Hey Sigrid, thanks for the feedback and your patience. Glad that Confluence databases is closing the gap on how Confluence and Jira work for you. 

I hear you, having a two way door to be able to edit Jira issues within Confluence seems helpful. This is something we will definitely consider in the future!

I'd love to also learn who in your company this feature would be beneficial for - someone who's looking at Jira issues in Confluence and wants to stay within the Confluence ecosystem? What teams might fall under this scope?

Sigrid H October 2, 2023

For us definitely the Product Management team, because while we track out tasks in Jira, all documentation/specifications live in Confluence. That means constantly hoping between the both tools. I think changing the status is the most frequent topic. But also things like assignee, labels or some custom fields. Another topic is that for documentation pages, we need to track which specifications introduce changes on the behaviour of a component. For this we also use Confluence, since the documentation part and linking pages is more helpful, but whether something has been released is stored in Jira. So here the more important part is displaying specific fields from Jira in Confluence. But the experience is that if you see the data in some place and then you notice some required adjustments, it is so much more convenient if you have some direct option and not need to leave the context you are currently in.

I can imagine that our operation team would also benefit from a tighter linkage between Confluence and Jira, but I don't know their processes that well.

Like Divya Sriram likes this
AUG Leaders

Atlassian Community Events