I am a PO and have a kanban for hi-level tasks based on multiple customers need, prioritisation, revenue generation etc - to score our backlog tickets for production (implementation) line.
Databases was a great addition and makes this much easier (I managed this earlier in a free-text table, requiring frequent manual interventions and updates).
What would be really valuable for us is to link from a ticket (issue) to all database entries where it is scored against a customer (a 1:n relation). So that when we open a ticket we can immediately see how it has been evaluated and estimate its priority.
I am pretty sure there are more doing this same way or planning to and therefor I'd like to ask if this will be a feature added?
Hi there
Perhaps with current functionality you could work with the "Jira Issue Field" and "Jira issue details field" in your database in Confluence?
Perhaps something like this in your database
Jira issue field - To add the issue
Jira issue details field - Status for the issue
Jira Issue details field - Customer name (if you have that defiened on the actual Jira-issue
Then you could use the filtering in the database to see the view you want to see. And can open the ticket directly from the database if you need to update anything.
Could also be possible to work with backlinks field if you try around a bit, but I don't really like how that displays in confluence database right now.
That doesn't still allow me to view the database references from the ticket - that's just viewing it from the database itself.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey, I think Jira Product Discovery would help you in this case. Confluence and Jira kanban board is not the best approach for a product backlog: https://www.atlassian.com/software/jira/product-discovery
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thx, I am hesitant b/c it is a paid product and I am currently not doing this on a scale to justify that. But keeping an eye on it - it may be what I need.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.