I'm investigating leveraging the Jira Issues macro in our QA Test Plans over tedious manual table creation. It's frustratingly close to what we need minus the ability to add additional text fields for comments etc.
Here's my question:
What controls the editability of fields in the macro? I see references that say it's entirely controlled by your permissions, but that doesn't seem to be so.
In the generated table of issues, I can edit the Summary, and even get a nice listbox to edit the Status. I cannot edit Comments, which I certainly can in the Jira Issue, I can't edit Labels, etc.
Are there rules beyond your Jira permissions that influence your ability to edit in Jira Issues Macro?
Regards,
Joel
Hi @Joel Ransom ,
It seems that not all fields are yet supported via the new Jira Issues macro.
However, it seems that support for these additional fields is in progress - see CONFCLOUD-54854: Update Jira issue from Confluence page. I would suggest leaving a vote and adding yourself as a watcher + maybe leaving a comment related to your requirement.
You might also want to check any other open suggestions related to this topic: project = CONFCLOUD AND resolution = Unresolved and text ~ "jira macro field editability"
I've not been using this editing approach that often, but I can see the benefits of having the ability to edit different custom fields directly in Confluence.
Hope this helps.
Cheers,
Tobi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.