Thank you for raising this issue. While we can see how this feature would be useful, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now.

Thanks again for your idea.

Bill Arconati,
Confluence Group Product Manager

Hey Sherif,

Thanks for your attention for this ticket.

1. This is really very similar to what we have now (Jira issue table). Difference is that Jira Issues table requires copy/paste of xml URL from Jira. (at least in my experience) 99% of the time, the jira issues displayed are "My issues for Jira project linked Confluence space". I am suggesting a very simple (no copy paste of URL from JIRA) macro that shows only issues assigned to me from the linked project. Another way to look at it, is the same as the Jira Dashboard Gadget "Issues assigned to me" implemented in Confluence and filtered to linked project. The customizability of the existing Jira Issues macro is great, but you have been adding more and more 1-click features to make common tasks quick and easy.

2. Yes, again my suggestion was around adding a 1-click (less customizable macro that automatically filters issues to linked project). Also a gantt chart or tabular view would be more useful than the calendar which requires click interaction to really see what issue are.

3. This is really about linking a page to an issue (finer grained version of linking a space to a project). If a page is linked to an issue and an attachment is added to the page, it would automatically show on the issue page. The Page tab you mention is interesting, but again, no link to Confluence (which seems the more logical place to store documents like a spec page).

Some overview, I am really looking at using Jira and Confluence for enterprise project management (not development). For a given project, a confluence space is created to host documentation, notes, anything that will need to be referenced in the future. A Jira project is also created but only used during periods of change/activity. Jira structure is too loose for finding design specs or created user guides later. Right now, Jira and Confluence are distinct entities, nearly no ecosystem benefit.

Travis, this is a tough feature request to keep open because it encompasses several feature requests, some existing some possibly new.

1. A quick macro that is 1-click implementaiton that just show all my Jira tickets from the project linked to this space?
What do you want from this? Do you really one a page to show all issues for a linked JIRA project? What is the goal of that page? Won't the page end up with 100s of issues?

2. A quick macro to display a project calendar/gantt chart on a wiki space home page?
You might want to check out Team Calendars for this. You can go Insert > JIRA Calendar, and then select your JIRA project and the dates you want to show and it embeds them on a Confluence page. So I think we have that feature today.

3 & 4. Add an attachment to the page and it is represented on the ticket? Add a ticket watcher and they automatically watch the page?
Could you give me a bit more context here? One of the things we talked about in the past is the ability to add a "Page" Tab to a JIRA issue. E.g.

The use case here of being able to embed a spec in an issue... is that your use case?