I would like to pull all the issues and sub-issues under Epics in my JIRA project and show them on a Confluence page; however, I want this listed out in a table structure (not just a simple JIRA issues macro) so that I can have a custom column with heading "Notes" for team members to add notes about each issue.
I do not want to add those notes in the JIRA ticket. The purpose is to capture notes/requirements and any pertinent details on deliverables associated with each ticket in Confluence. That way the critical info is available in Confluence but if team members want to find out more then they can look into Jira. My assumption is that the JIRA board will not be around as long as the Confluence board.
Is there a way to do what I'm asking or maybe an alternative?
Thanks
Thanks for the reply, Jobin, but unfortunately that's not what I'm looking to do. That is actually what I was doing originally but it's a tedious process so I've resolved to the traditional JIRA issues list macro and adding an attachments macro for any additional documents until there is an implementation for a feature like what I'm asking.
You will have to create a table and add the issue keys alone (using the issue macro), instead of the filter. The table won't be dynamic though. i.e. it won't pull new issues to Confluence automatically! Will that work?
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.