Two big wishes - all the macros should support user specific authentication and JIRA running over https. If the requirement for the user specificity to work is that Confluence has to use the a shared user DB, that's fine by me.

It would be nice to have a macro that creates a table of jiraissues in children pages. If it also summed tasks in the tasklist macro, it could be used in creating a project.

This way one could start a project with a bunch of vague tasks described in Confluence. As implementation gets under way, features are specified as a bunch of jira issues displayed with the jiraissues macro.

jonas

It's nice to have 2 variants of jiraissue:
1. Displays issue details (description, etc.)
2. Just displays the issue key (which is a link), which is striked through, if issue is already fixed, has the color of issue priority & has the issue type icon. (The latter two should be optional). Like: JRA-1234, JRA-4321.

For any of these, please make sure they respect the current image settings in JIRA for replacement icons for those attributes such as priority, issue type, etc. Those must therefore be retrievable from the JIRA remote API.

Would like to have a macro for a jira data entry form so you can embed a quick "create issue" form within a Confluence document. We usually create simple ones by hand right now using the html tags in Confluence so that we can in-line a quick form without the user having to see the full form that we would use internally in the technical group.

I guess Jason is referring to this: CONF-1415? One additional issue with the icons is that if Confluence and Jira is protected using HTTPS, loading the icon images from Jira on another machine fails because of browser security restraints. Hence Confluence should load the images from Jira and serve them locally.

I've been playing with the jiraissues macro a bit and found how to display issues within a project using a separate macro for each component in a project, however it would be real nice if the list of columns in the table wasn't restricted to a limited set of fields. Specifically, if I create a custom field for a "New Issues" form for a specific project I'd like to be able to display the value of that field in the resulting output using the jiraissues macro.

If the source of the macro were available I imagine that it wouldn't be too difficult to implement.

I also found that the macro is poorly documented, specifially in regards to the url that needs to be provided.

How about a roadmap macro. Now that would be cool.

I would like to see a jiraissues like macro/portlet that gives a list of issues (from a filter) and allows expansion/contraction of the description (and other fields) using capabilities like the cloak macro.

What about JIRA and Confluence being able to log-in to one another so that they can trackback and automatically create links to each other without adding username and passowrd to macro and "slip in" the others secruity?

What is the status of those macros?

What is the status of the JiraIssue macro?

jiraissue - Display details about a single JIRA issue with in Confluence, available via the new remote XML issue view feature.

I am surprised you haven't implemented all of these - the workflow features of Jira could add so much power to Confluence if they were more tightly integrated. I would have thought that integration between your products would be a high priority.

Jira and Confluence have infiltrated right into our SDLC process now - Jira for all project tasks (i.e. no one can do any work without a Jira issue), and Confluence for all project doco. (See the Subconf plugin: http://confluence.atlassian.com/display/CONFEXT/Subconf). In some projects, the full SDLC lifecycle is modelled in Jira as a custom worflow.
So we end up creating Jira issues where the subject of the issue is a Confluence page, but the whole process is manual. Tighter integration could add a lot of value.

This is the way I see it:
Jira Project associates with Conf Space - this should be a setting both in Conf and Jira. Need a space admin page to select a Jira project for the space.
Jira Issue associates with Conf Page - this could be stored as a page property in Conf, and as a Link in Jira.

Basically what I would really like is a new tab in Confluence that
1. Shows any Jira issues associated with this page, their info (including status) and also allows you to cause workflow actions such as resolve.
2. Allows you to create a new Jira issue that is automatically associated with this page. Maybe defaults the issue title to the page name?

Maybe also a macro to show the above info in the page content itself would be useful.

Maybe you could also associate Components and Versions with page heirachies and default new issues in the heirachy with those components and versions. Maybe also there is a mapping between labels and components and/or versions.

We also use CONF and JIRA and are waiting for an improvement of the jiraissue macro

We also use Confluence and JIRA and would like to know the status of this...