Editable Jira work items tables

[quinton_lawman]

I have a series of tables that I've added using the Jira work items macro.  These tables are not editable in Confluence.

What I'd like to do is add a column with a checkbox that a 3rd party can use to check off their side of the work.  Or, maybe add a column for notes.

These new columns should not change the Jira tickets at all.  This is just a way for me to add information to a table of Jira tickets that people who do not work in the Jira space can see and/or act upon.

Is there any kind of solution for this already?  I can insert a table next to these work items tables, but the rows don't line up and that's . . . less than ideal (and extremely manual).

[Germán Morales]

Hi @quinton_lawman , welcome to the Atlassian Community!

The Jira work items macro cannot be extended with editable Confluence-only columns. It can show, hide, and reorder Jira fields, but it does not let you insert a notes or check-off column into the generated table.

The closest native solution is to replace that macro with a Confluence database:

• During database setup, connect to Jira and insert the required work items.
• Use Jira work item detail fields for the key, summary, status, assignee, and other Jira data.
• Add a Text field for notes and a single-select Tag field such as Pending or Complete for the third party.

The Jira detail fields remain read-only in Confluence and update when their Jira values change. The Notes and third-party status fields are stored only in Confluence, so editing them does not modify the Jira work items. Give the third party edit access to the database and test the linked Jira-field visibility with their account before replacing the existing tables. Atlassian describes the available options in its database fields documentation.

[Tomislav Tobijas]

Hey @quinton_lawman ,

Did you manage to get around this? As German said, databases would be the best bet. I even think we build a solution with databases for really similar requirement. (And from what I remember, it worked pretty well 🙂)

Apart from that, you could think about using Tasks/Actions and Task report macro, but I still think database would be a better choice.

Potentially there are some Marketplace apps, but native features should probably do the job.

Cheers, Tobi