JIRA is the issue tracking and project management system supplied by Atlassian. By adding the JIRA Issues macro to a Confluence page, you can display one or more issues from a JIRA site. You can also choose to create an issue in JIRA, at the time of adding the macro to the Confluence page.

Before you can use this macro, your Confluence and JIRA sites must be connected via Application Links. People viewing the page will see the publicly accessible issues from the JIRA site. If your JIRA site has restricted viewing (that is, people need permission to view issues) then they will need to authenticate before seeing the restricted issues. See more about restricted JIRA issues below.

If you want to customise the display, choose Display options and adjust the columns and number of issues that will appear in your table of issues.

Choose Insert.

Screenshot: Display options in the JIRA Issues macro browser.

Displaying issues via a JIRA URL

You can paste any of the following JIRA URLs into the JIRA Issues macro. Confluence will immediately convert the URL to a JQL search.

Any URL for a JIRA issue search or filter.

A URL for a single issue.

The URL of the XML view of a JIRA search.

Auto-convert: You can paste a JIRA URL directly into the Confluence editor (without calling up the macro browser). Confluence will automatically convert the URL into a JIRA Issues macro.

Displaying a single JIRA issue, or selected JIRA issues

To display a single JIRA issue, choose one of the following methods:

Paste the URL of the issue directly onto the Confluence page. (There is no need to use the macro browser.) Confluence will auto-convert the link to a JIRA Issues macro.

Or: Add the JIRA issues macro to the page as described above, and choose Recently Viewed to see the JIRA issues you have visited recently. Select an issue and choose Insert.

Or: Add the JIRA issues macro to the page as described above, and paste the issue URL into the search box in the macro browser.

Or: Add the JIRA issues macro to the page, define your search criteria in the macro browser via JQL as described above, then select the check box next to the issue in the search results, within the macro browser.

You can choose to show just the issue key, or the issue key and a summary. Select the macro placeholder and choose Show Summary or Hide Summary.

To display a subset of JIRA issues from your search results:

Add the JIRA issues macro to the page.

Define your search criteria in the macro browser via JQL, as described above.

Select the check boxes next to the required issues in the search results, within the macro browser.

Screenshot: Selecting a subset of issues to display

Displaying a count of issues

You can choose to display the number of issues returned by your search, rather than a table of issues. The JIRA Issues macro will display a count of issues, linked to the search in JIRA.

Screenshot: The JIRA Issues macro displaying an issue count on a Confluence page

To display an issue count:

Add the JIRA issues macro to the page.

Define your search criteria in the macro browser via JQL, as described above.

Choose Display options, then choose Total issue count next to 'Display options' in the macro browser.

Choose Insert.

Creating a new JIRA issue in the editor

While editing a Confluence page, you can create an issue in JIRA and display it on your Confluence page, without leaving the Confluence editor.

Supply the information about your JIRA server, project, and issue, as prompted.

Choose Insert.

Confluence will send a request to JIRA, to add the issue to the JIRA site. Confluence will also display the resulting JIRA issue on the Confluence page.

Limitations

The JIRA Issues macro will notify you if it is unable to create an issue in the selected project. This may be because the project has a required field, field configuration or other customisation that is not supported by the JIRA Issues macro. In this situation you will need to create the issue directly in JIRA.

Configuring Application Links to display restricted JIRA issues

Before you can use this macro, your Confluence and JIRA sites must be connected via Application Links.

If the JIRA site allows anonymous viewing of issues, you must configure an application link, but there is no need to configure any incoming or outgoing authentication between JIRA and Confluence. People viewing the Confluence page will see the publicly accessible issues from the JIRA site.

If your JIRA site has restricted viewing, or if some JIRA projects or issues are restricted to viewing by certain people, then people will need to log in before seeing the restricted issues.

In such a case, the outgoing authentication in the Confluence Application Links determines how the JIRA Issues macro handles restricted issues:

If the outgoing authentication is set to Trusted Applications, people can see restricted issues in JIRA if their username is the same in JIRA and Confluence, and if they have permission in JIRA to see the issue.

If the outgoing authentication is set to OAuth, people may need to choose Login & Approve, to gain access to the JIRA server and restricted issues.

If the outgoing authentication is set to Basic Access, people can see the JIRA issues that are visible to the user account configured in JIRA's outgoing authentication setting.

Rendering HTML from JIRA

Formatted fields from JIRA can be displayed in Confluence if you set up a Confluence-to-JIRA application link. Otherwise, such formatted fields will be escaped within the output of the JIRA issues macro. This is to prevent the possibility of malicious HTML being served by an untrusted JIRA server. The most likely field where you will notice this is in the description field.

This example shows how a description column may be displayed in JIRA:

Description

This is

the description

of my issue

If there is no application link between JIRA and Confluence, the description will appear in the JIRA issues macro like this:

Description

<p>This is<ul><li>the description</li><li>of my issue</li></ul></p>

Disabling the JIRA Issues macro

The functionality is provided by an add-on (plugin) called 'JIRA Macros'. To make the macro unavailable on your site, you can disable the add-on. See Disabling and enabling add-ons.

Custom fields can be added as columns to the table simply by using the name of the field with no quotes. Earlier versions of the macro required you to use the custom field id, e.g. customfield_10100.

Code examples

The following examples are provided for advanced users who want to inspect or edit the underlying markup for a Confluence page.

Macro name:jiraissues

Macro body: None.

Note: A number of additional parameters that are not available via the macro browser are available in storage format and wikimarkup.

Parameter name

Required

Default

Parameter description and accepted values

anonymous

No

false

If this parameter is set to 'true', JIRA will return only the issues which allow unrestricted viewing. That is, the issues which are visible to anonymous viewers, as determined by JIRA's viewing restrictions. If this parameter is omitted or set to 'false', then the results depend on how your administrator has configured the communication between JIRA and Confluence. By default, Confluence will show only the JIRA issues which the user is authorised to view.

Note: This parameter is available only if you insert the macro via wiki markup or by editing the storage format of the page. The graphic user interface (macro browser) for the JIRA Issues macro does not offer this parameter.

baseurl

No

The value of the 'url' parameter

If you specify a 'baseurl', then the link in the header, pointing to your JIRA site, will use this base URL instead of the value of the 'url' parameter. This is useful when Confluence connects to JIRA with a different URL from the one used by other users.

columns

No

By default, the following columns are shown:

type

key

summary

assignee

reporter

priority

status

resolution

created

updated

due

A list of JIRA column names, separated by semi-colons (;). You can include any columns recognised by your JIRA site, including custom columns. See the JIRA documentation for a list of names.

count

No

false

If this parameter is set to 'true', the issue list will show the number of issues in JIRA. The count will be linked to your JIRA site.

cache

No

on

The macro maintains a cache of the issues which result from the JIRA query. If the 'cache' parameter is set to 'off', the relevant part of the cache is cleared each time the macro is reloaded. (The value 'false' also works and has the same effect as 'off'.)

Note: This parameter is available only if you insert the macro via wiki markup or by editing the storage format of the page. The graphic user interface (macro browser) for the JIRA Issues macro does not offer this parameter.

height

No

480 (if render mode is dynamic)

The height in pixels of the table displaying the JIRA issues. Note that this height specification is ignored in the following situations:

If the 'renderMode' parameter (see below) is set to 'static'.

When the JIRA issues are displayed in a PDF or Word document, in an email message or in an RSS feed.

Note: This parameter is available only if you insert the macro via wiki markup or by editing the storage format of the page. The graphic user interface (macro browser) for the JIRA Issues macro does not offer this parameter.

renderMode

No

static

If the value is 'dynamic', the JIRA Issues macro offers an interactive display which people can manipulate as follows:

Click the column headers to sort the output.

Drag and drop the columns into a different order.

Temporarily remove a column from the display.

View a page of issues at a time, for faster response times.

A value of 'static' will disable the dynamic display features.

Note: This parameter is available only if you insert the macro via wiki markup or by editing the storage format of the page. The graphic user interface (macro browser) for the JIRA Issues macro does not offer this parameter.

title

No

JIRA Issues

You can customise the title text at the top of the JIRA issues table with this parameter. For instance, setting the title to 'Bugs-to-fix' will replace the default 'JIRA Issues' text. This can help provide more context to the list of issues displayed.

Note: This parameter is available only if you insert the macro via wiki markup or by editing the storage format of the page. The graphic user interface (macro browser) for the JIRA Issues macro does not offer this parameter.

url

Yes

none

The URL of the XML view of your selected issues in JIRA Issue Navigator.

Note: If the URL in the 'url' parameter does not contain a tempMax argument, then the value of tempMax will default to 500. If your JIRA server is version 3.12 or earlier, this means that the JIRA Issues macro will return a maximum of 500 issues. If your JIRA server is version 3.13 or later, a value of 500 means that the JIRA Issues macro will return a maximum of 500 issues per page.

width

No

100%

The width of the table displaying the JIRA issues. Can be indicated either as a percentage (%) or in pixels (px).

Note: This parameter is available only if you insert the macro via wiki markup or by editing the storage format of the page. The graphic user interface (macro browser) for the JIRA Issues macro does not offer this parameter.

Storage format example

Example using a URL that points to the XML view of a JIRA search:

Example using JQL – note that Confluence will insert the server and serverId parameters, based on settings in Application Links:

I expect the problem's due to a saved filter in JIRA that's private, and the lack of authentication credentials passing between Confluence 2.7 and your JIRA.

It may be that you only need to go into JIRA, manage your filters, and mark this particular one as shared (or global or whatever). Else, you need to look up the method of passing credentials in your jiraissues macro call – but you could instead try Setting Up Trusted Communication between JIRA and Confluence with an updated Confluence.

Quick question. The jiraissues macro does seem to work well now that we have trusted communications set up (Jira Enterprise Version 3.12.1 Build Number 299, confluence 2.8 enterprise); however not all the icons show up properly for the field type and priority. Looking at the html I see for the issues that it does show up for the hmtl looks like: src="https:ourservice/jira/images/icons/issue_subtask.gif; whereas for the ones that don't show up we have <img src="$icons.get( $item.getChild('type').getValue() )".

Note that on Safari I see a broken image link. On Firefox I get the type or priority text as a hyperlink.

Thoughts on what's going on? I suspect that the type and priority that aren't showing up are ones we created in JIRA, but we're using the default icons w/in JIRA so I'm curious about what we need to do to have the icons appear.
thanks

Could you please check that the image's URL of the same issue type does match each other in Confluence and JIRA? You might also want to make sure that the icon mappings are correct, if you have any custom issue types:

Anonymous

Hi, we are currently encountering issues when displaying {jiraissues}

We have done various things to remedy this:
1. Ensured user is logged in on both wiki and jira and is using the same userid
2. Increased the Request timeout in Jira and Wiki (2000000)3. Ensured the IP Address Matches are correct on both Jira and Wiki Trusted App setup.4. We've checked the logs (catalina.out/access_log.2008-10-08) and we dont see any weird exceptions.5. We've tried flushing cacheBut the error is still there. The most recent activity prior to this happening was we restarted our server.Pls advice.

this error may be caused by incorrect macro parameter usage (for example, putting something other than the url param in first spot and not marking it with "columns=" or whatever). not sure what was happening here but i guess you got it fixed because you give a new error below. (new errors mean progress, yay! )

We have done various things to remedy this:
1. Ensured user is logged in on both wiki and jira and is using the same userid
2. Increased the Request timeout in Jira and Wiki (2000000)3. Ensured the IP Address Matches are correct on both Jira and Wiki Trusted App setup.4. We've checked the logs (catalina.out/access_log.2008-10-08) and we dont see any weird exceptions.5. We've tried flushing cacheBut the error is still there. The most recent activity prior to this happening was we restarted our server.Pls advice.

This error occurs when the macro has trouble parsing the XML returned from JIRA. This can occur if the url given to the macro points to something it shouldn't, but it could also mean the macro is encountering valid XML that it isn't expecting for some reason. We should probably have better handling of these cases...

Two common ways for this to occur:

JIRA is down - the retrieved info could be an html error page that can't be parsed as xml because it isn't

url is not the XML view url

If the above cases aren't the problem, please create an issue about this, including your JIRA Macros Plugin version and ideally the macro syntax you are using and the XML file that is returned by JIRA when you visit the url given in the url parameter.

the latest version of this plugin, which is currently used here on confluence.atlassian.com though the version of confluence this plugin is bundled with is not yet released (we're testing it out here), includes a height but not a width parameter. the previous version included neither height nor width parameters.

This error occurred for me also. I'm using Confluence 2.10 and JIRA 3.13. In my case, it appears to be related to using a https url. When I changed my url to point to the http address, the error did not occur and I could see my issues.

That old chestnut. you need to import the Certificate Authority (CA) that signed your SSL certificate into the Java Runtimes trust store so that when Java connects with SSL, it is able to walk the chain of signers and verify its authenticity. No CA = untrusted certificate = no ssl connection. If you have a self-signed cert, just import that instead. Oh, and the SSL server FQDN does match the CN of the certificate, right?

In addition to importing into the trust store you may need to explicitly identify its location and passphrase to open it. Default JRE trust store location is JAVA_HOME/jre/lib/security/cacerts. changeit is the default JRE password, really.

Get the signer cert (exercise for the student ) and do this from the security folder:

Is there any way to parametrically specify the query parameters (ie. specify the same type of information like desired user, status, date range)? Basically, generate a dynamic filter at page load time, rather than having to reference a pre-made filter in JIRA?

For example, it would be nice to have a filter for "show me the issues marked 'closed' for user in the pastdays".

Then, in some Confluence page, do

or

It appears to me the answer is "no, neither {jiraissues} nor JIRA itself can do that". Without this capability, I'd have to create separate filters in JIRA for "Bob @ 30 days" and "Frank @ 7 days", which is not desireable. Is that a correct assessment? Where would I create such a feature request? It would greatly improve Confluence<->JIRA integration, in my opinion...

If you wish to modify your JIRA Issues macro filter with the specific parameters you have described, you currently have to recreate the JIRA query as described in step 1 above.

When you create a JIRA query with your specific filters, the parameter-value pairs that represent each specific filter will be present in the XML link URL. If you make a note of these parameter-value pairs, you could insert them directly into the URL contained within your {jiraissues} command in Confluence. However, be aware that we currently do not support this approach.

I will adapt the plugin as the link should contain the key, and I can't expect that the users are going to fill in the custom field,
unless there is a way to automatically generate the content of that custom field

there should be a way to generate the field contents in jira, but i think if you can adapt the plugin that is the way to go since you can get more precisely want you want. (if you made a link custom field, the other columns in the jiraissues table would still use the non-preferred link and that could be confusing for users.)

Macro works fine, but I am wondering if there is a way to configure the display so that table hight automatically adjusts based on the number of issues. In some cases we do not have many issues and 'large' blank space between the issues and page number footer is looking ugly. If I remember correctly we did not have this problem with 2.5.6 version confluence we were using earlier. We are currently using confluence 2.10 and jira 3.13.2. Our users are complaining about this display and it would be nice to have a solution.

no, you cannot have the height auto-adjust based on the number of issues returned. one reason is that the amount of space each row takes is browser and user settings dependent, so the correct height to auto-adjust to is not apparent.

you are correct that the older version of the jira issues macro did not have this issue, because it wasn't dynamic and was using a different ui. you can force the old style ui to be used with the renderMode=static parameter, but you will lose the new dynamic features. you might instead use the height parameter to manually set the height you'd like.

Hello Cheryl - your tip on the renderMode=static was exactly what I was looking for as I'd like to limit the real estate this macro takes up on the confluence page. I have a use case where I need to display a single issue and 3 fields. Is it possible to limit the macro with other parameters to get something like this (without the issues header to sort)?

I still seem to have difficulty getting any custom fields displayed - I have Confluence 2.7.1 and Jira 3.11 and my macro is as follows (with the usual sensitive info changed to protect the guilty..)

My regular fields show up just fine, but even when doing a 'view-source', it's like Confluence doesn't even see that column coming back.. I've played around with the order of the columns in the string as well as tried other customfield items with no luck.

displaying custom fields with the jiraissues macro was added in a version of the plugin that is unfortunately not compatible with confluence versions less than 2.10 (and it is bundled there). also, the name of the field is used in the columns parameter rather than the id.

Is there any workaround to put a width setting in. It's important for the way our system is configured. As 100% width is breaking things on our end.

Just to followup, this page is suffering the exact problem our site is having. We insert the tree on the left side of most of our pages. If there is a jira object on the right it pushes the scroll bar all the way to the right, and it smooshes the tree navigation.

Although above comment says "Unable to determine if sort should be enabled", that wasn't actually the error Adam was seeing (CONFJIRA-130 was actually fixed – check the source tab to see the code changes). Confusingly, it is just the error when his comment tries to render an example macro with incorrect syntax.

However, there was another issue for the problem you describe: CONFJIRA-154. (BTW, you'll notice that the issue was fixed by improving the error messages, so you may be able to get a better error message by upgrading your plugin version.) If you can't find the problem from that issue, you'll want to create a support request so our support team can help diagnose your individual situation.

Anonymous

The size of a jiraissues macro pane defaults to about double the width of a standard browser, and fills most of the hight of a standard browser window. The font is also unnecessisarily large and there is far too much whitespace and wasted space, even in the example on this page. (The control bar seems reasonable, though). Is there a way to reduce not just the width and height of the window, but to reduce the scale of the entire widget as a whole, including font size and table cel and header size and spacing?

i don't think there is a built-in way to change the scale. you could try modifying the plugin's css to your liking, by creating a new version of the plugin itself or by using a tool such as greasemonkey to modify the css on the fly locally

I really like this makro - but I have one problem:
We always use anonymous = false, and if I don'T have enought permissions, I get:
"jiraissues: Error on line 6: The reference to entity "N" must end with the ';' delimiter."
as an error massege in Confluence.
This makes in quite unusable for us because we never want to see a customer of us to see a technical error massege like this.
Is it possible to replace it quickly with one like "Sorry, you don't have permission to see the issues" in the next days?
(We are using Confl 2.9.1)

What you describe sounds like it could be a bug. If you can provide more details, we can investigate it further. You can create an issue in the Jira Macros Plugin project. Please provide the macro syntax you are using and a saved copy of the XML that you get when visiting the location in the url parameter. If this information should be private, you can mention that in the issue and mark the security level as "Reporters and Developers".

However, note that the latest version of the macro is not compatible with Confluence 2.9.x and there have been many bugfixes and new features since the older macro version was created. So, we may find that the best solution to your problem is to upgrade Confluence and the macro.

What I meant by "nicely" is in confluence 2.9 the summary field does not take over the whole space, you can see the other colums - it seems like the size of the summary column is dynamic and shrinks so the other columns can be displayed on the screen. With 2.10 version if summary if the first colum it fills the display window and you have scroll to see the other columns, So we have to place the other columns ahead of the summary column. In some instances that works ok, but in other places it makes the information a bit awkward in presentation.
Does that make sense?

Have a filter in Jira that displays an Issue and it's substasks using two components to get the issue and subtasks I want. It displays correctly in Jira.
when I copy the xml to Conflunce to do up the JiraIssues macros I get nothing but the header for the filter and no rows for the actual task and sub tasks. The name of filter is there with zero issues and column names are listed.

I could not replicate this on a local instance. Perhaps, you can try creating a saved filter in our JIRA and see how it goes. I presume it does not affect unsaved filters or any other saved filters? Although it is not likely to be an issue, you might want to ensure the credentials are correct.

Sorry that I didn't realise that you are using Confluence 2.9.2, hence the latest plugin version compatible is 2.8.1.2. In order to get more fields displayed, you will need to upgrade to Confluence 2.10.x (plugin version 2.8.7 - a new plugin architecture has been implemented, hence incompatible with Confluence pre 2.10.x).

Thanks for creating this list Bernhard, I think it will be useful for many people.

In general, the column key you give to the Jiraissues Macro should match the name of the field as written in the issues XML. So if you are having problems getting a particular field, make sure those names match.

It's like Bernhard wrote, e.g. in JIRA its called Sub-Tasks in jiraissues its stated subtasks. There are quite some doubts with this "implementation", e.g. the subtasks are not rendering as links and they dont get linefeeds for each entry (more than one isnt displayed as from the second one it gets hidden).
I hope the jiraissues-plugin gets a 3.0 that deserves this name, with complete documentation, nice scaling and maybe some more parameterized settings. Cant really enjoy myself with the new fixed height and with of the macro.

Edit: After some digging, found some more interesting fields on time tracking (Aggregate fields):

Anonymous

When following the procedure to include a JIRA issues list, I cannot get the XML url to correctly display all of the issues. Only the first issue is shown, but not the newly created ones. Any clues what I am doing wrong?

My filter in JIRA does correctly show all three issues, and the MaxTemp parameter is set to 1000 but only 3 issues in this test project.

some of the issues are not visible to anonymous users, and you haven't provided the macro url with authentication parameters and trusted apps is not configured - if this is the case, see the Displaying Issues which have Restricted Viewing section above

you are getting a cached view of the issues - try clicking the blue refresh button to see if the additional issues show up and consider using the macro parameter cache=off

Displaying custom fields with the jiraissues macro was added in a version of the plugin that is unfortunately not compatible with Confluence versions less than 2.10, because creating the plugin's new features required adding features to Confluence first.

Anonymous

We are currently using Confluence 2.10.2 and JIRA 3.13-#330. When we display the JIRA issues in JIRA the headers are in French. However, when using the jiraissues macro in Confluence the headers are in English. Both JIRA and Confluence are configured to display in French. How do I obtain the headers in French?

you can probably change that by changing the jiraissues.properties file. Either by compiling the plugin or maybe in the classes folder of the webapp. There you can specify the Column-names for your Confluence-installation (it will be consistent for all macros, its not parameterizable, so far), looks like:

analysed it a bit more. The jiraissues.properties file is the default one. It is already the i18n-file. So if you want a German locale you just copy this and rename it to jiraissues_de.properties (accordingly for french, of course). A German locale would look like:

I have a custom 'User Picker' field which I want to display. When using the issue navigator in Jira, the persons full name is displayed, but the jira issues macro displays the username. Is there a way to get jiraissues to display the fullname rather than username?

jiraissues macro does downloading and extracting the data from an xml (if you click xml link from the issue navigator). By default, the xml link does not display the value of fullname but it does display username only. That's why jiraissues cannot display the fullname because the data is not there. In order to make jiraissues can display the fullname, you need to modify behavior of jira (customize jira core code) so that when you click the link xml (to generate an the data in xml format), it will give you fullname.

So the height and width allow me to ensure that the table fits into the page. That is great as far as it goes.

The problem is that when you have say a long description and a long summary, the actual content is more than will fit in the width of the page. What I want to do is force word wrap in a column (say description) so that a user only need to scroll vertically to see all of the content of the table.

As is stands now, the user will have to scroll both horizontally and vertically to see the entire table.

I am not able to see Component/s column via jiraissues macro (usage ...|columns=type;key;summary;component) and I am not able to see the navigation bar ... any idea what version of JIRA/Confluence this two functionalities were introduced?

Hello, Theodor. Those features were introduced in Confluence 2.10. I would suggest you to upgrade your Confluence to the latest version available, since the plugin version that contains those features is not compatible with Confluence 2.9.x. Hope that helps!

I just got this same error, but on 2.10.3, it transpired an apache server was down which was previously handling old URL redirects (error message wasn't terribly informative in this regard ). Validate your filter url in a browser, perhaps you have a DNS or similar lookup problem.

Indeed, the error message isn't very helpful. Thanks for your quick reply - I tried to view the filter url locally from the server and indeed, it cannot resolve the host name. Thanks for the pointer :)

The macro should work in Confluence 3.0, because the plugin that contains it is supported for that version. (And I can confirm that it works for me personally.) So if you are having problems perhaps there is a Confluence bug or a configuration issue occurring. I see you've created a support case, and that is great because support should be able to help track this down.

We've currently got JIRA and Confluence on the same server both listening on port 8080.

As we're getting more and more people on board we'd like to tidy up the URLs. So we plan on moving both Confluence and JIRA onto Port80 and we'll probably move to a more meaningful URL.

We use the jiraissues extensively and so we'll have to edit a lot of pages to fix up the URLs.

Between now and when we do the URL tidying is there a way to soft code the Jira URL in the Jira Issues macro? A sort of extension to the short cut links? What is best practice? (Other than getting it right to begin with).

Is it possible to disable the Issue Type text instead of the icon? We've created many custom issue types and they are all using the generic icon. We could create custom icons, but it would be simpler to just display the issue type as text

Is it possible to disable the Issue Type text instead of the icon? We've created many custom issue types and they are all using the generic icon. We could create custom icons, but it would be simpler to just display the issue type as text

Thak you for this great stuff.
I'm having a problem here, we have some custom field using datepicker data type, it's showing fine on the page view.
but, when we try to send the page by email, it will showing a complete formate datetime just like this : Wed, 21 Oct 2009 00:00:00 +0800 (SGT)
also on the received email

is there anyway we can fix it in our side? or is it a bug?

the second problem,
I was creating a filter and forgot to add the share, and then the macro won't showing the issues event after I add the share, and i have to create a new filter to have it showing correctly. in other case, the issue not showing all the issues ont the filter, which is also fixed by creating a new filter. is there any synchronization problem on this macro?

This is not a big deal but doesn't hurt to ask. I haven't seen it documented anywhere (I'm hoping it's there, but just not documented): is there a way to tell jiraissues to only show an arbitrary list/set of issues? i.e. show me QA-453, SYS-4432 and SYS-4431 only? They way I do it now is I just make sure I can search that set of JIRA issues, and that use that "XML link".

As far as I'm aware, there are no other parameters of this macro (apart from the url one) that you can use to control the filtering of results retrieved from a JIRA site.

Furthermore, you should probably only restrict your results using the search and querying tools in JIRA itself (i.e. the way you're currently doing so), since the XML link is generated from these JIRA searches and queries. Editing this XML link to filter your result could be quite tricky and not a recommended approach.

If you would like to see filtering features introduced into the JIRA issues macro, please raise a New Feature request on our JIRA site.

Another suggestion, you could also request that the administrator of your Confluence site configure shortcut links to your JIRA site. Hence, if they configured a shortcut link key of JIRA with an expanded value of http://<URL of your JIRA site>/secure/QuickSearch.jspa?searchString=, then you could use [QA-453@JIRA] to create a Confluence link which leads directly to that issue on your JIRA site.

I would like to track the status of a single parent issue and all its children on a confluence page. I've tried feeding the jiraissues macro the XML path from the parent issue, but the macro returns "jiraissues: Unable to determine if sort should be enabled". Does jiraissues support this use case?

I don't think that use case is supported. I think the XML URL must be a search result URL. One possible workaround would be to put a label on the issues you want to track together (e.g. the parent and children) and then do a search for items with that label.

Is there a way to set the Issue Macro to Shrink in height based on the issues that are displayed?
If number of issues exceed the height then we seen it traversing the pages which is fine but if the number of issues are less I the macro should shrink so that it does not eat up the space. Also it looks ugly

Ho can I incorporate "Issue Links" in this macro? "Issue Links" is available in JIRA Issue Navigator and shows all the issues that are linked to this issue. I would like to have the same capability in my JIRA Issue Macro as well

You can get a not-super-pretty list of issue links by adding "issuelinks" to your "columns" parameter value. I created an issue for improving the display. Feel free to submit other bugs or feature requests there if you have them.

I found a workaround for the not-super-pretty style of issuelinks field. You can use table-plus macro enclosing the jiraissues macro to insert some style attributes to the columns of jiraissues table. You will need to use renderstyle static. Here is a working example:

This solution may not work in every environment (dependent to JIRA version, Confluence Version and browser). I was using JIRA 4.1.1, Confluence 3.1.1 and Firefox 3.16.13. The used CSS style attribute "white-space:normal;" is in conflict to HTML "no-wrap=true" that is embedded in HTML code of jiraissue macro.

Shortcut links are actually created with another plugin, which wouldn't modify parameters to macros in other plugins. Anyway, I would think the shortcut wouldn't be so useful because most jiraissues URLs would be copied directly from JIRA, but maybe I am wrong, so you can create a feature request for that.

Anonymous

Hi,

Everything is coming over from Jira nicely, however, the Jira field "Documentation Link" (which presents itself as a hyperlink when in Jira), is being displayed as simple text. Is there a way to have the Documentation Link content act as a hyperlink?

Hi Andrew,
Unfortunately, jiraissue macro is not able to render hyperlink. Please feel free to create a feature request to enable hyperlink in jiraissues macro, share your comment over there, vote on it , and add yourself as a watcher for future update. Please also take note on how we implement feature request.

Hope it helps. Please feel free to ask again if you need further assistance.

When I am using this to show sub-tasks of a specific parent, I can't seem to get them to show in the order in which they are set within the parent task. I've got my filter as a "parent = [parentkey]" query, but the order that the parent is allowing me to set on the sub-tasks doesn't seem to be exposed as a field that I can sort on. Does anyone know the field name? Or is that a part of the link itself, and not the record? If so, is there any way to do this?

When looking at the sub-tasks shown on an issue, there are little "up" and "down" arrows that allow me to change the ordering of the sub-tasks as shown within that list. When doing the "parent = ﻿parentkey" query to retrieve the sub-tasks, the records that are returned are not in the order set in the list shown on the parent record. I'm not seeing a field that would seem to store this value on the sub-task itself (which are the only fields that appear to be available for use within the ORDER BY clause). I'm thinking that the index is stored on the link between the parent and the sub-task? Or perhaps I'm just missing the field?

Perfect, thanks! In the mean time I actually turned to the XSLT macro and was able to pull the and format items that I wanted. The only problem there is that I needed to pass in a username and password (as is documented in the old jiraissues macro). It would be great if you guys could implement a more generic solution that allowed any macro to talk to confluence from within an authenticated channel, without the macro needing to be aware of the auth.

Anonymous

Hi,

after a while I found how to add a custom field to be displayed with the jiraissues macro. But I had to change the name from "My Custom Field" to "MyCustomField" otherwise the field will not get displayed. Did I miss something or is ther no way of adding human readable custom field names?

Anonymous

Hi Claudia, did you manage to solve this? I have the same problem when selecting the renderMode=static i.e. the fields in my static column does not display in Confluence. Only when I leave the columns field empty will my information display correctly.

I have added a custom field which can have quite a long string, but the default width (Summary is always the largest - and that is not what I always require..) means that the user has to manually resize every time the screen is loaded. I haven't been able to see any discussion of this feature/requirement...

I'm having the same issue. I have a custom field to document an external release note and I have to use that field because of the character limit on the Summary field. Hopefully there's a workaround. Also, is there a way to concatenate fields? For example, put the contents of the Summary field and my custom external release note field into a single field when displayed in Confluence?

Anonymous

Anonymous

We are encountering a similar error reported by several: jiraissues: Unable to determine if sort should be enabled

It came about when we upgraded from 2.10 to 3.2.1_01; our jira version is: 4.1.1#522).

I followed the documentation instructions just to reinsert/copy the xml link.

I tested the link by putting it into a separate browser window to make sure that it rendered correctly

They are not setup with SSL, so a trusted connection between confluence and jira should not be necessary

I tried with a specific user's set of credentials (as was necessary with our 2.10 version) and it still should have worked, even though it's not recommended -- but, it didn't. I tried with anonymous set to TRUE as well.

We uninstalled and reinstalled the plugin

We reviewed the error logs to ensure we weren't getting an issue with host name validation -- couldn't locate any such error message.

Does anyone have any other suggestions for how to troubleshoot this issue

On this custom field Release Notes Comments, defined as type Free Text Field (unlimited text), we introduce all information we consider should be known by other teams about a particular issue on a language that's easy to understand for them. Then we automatically collect all those release notes using the jiraissues macro and that constitutes our release notes for a particular version.

I am nevertheless experiencing two issues with it:

First, it is not wrapping the lines of text, so that I actually have to insert breaklines at strategic points within the Jira's Release Note Comments field so that the lists of issues do not expand horizontally too much. The lines are being perfectly wrapped in Jira, where everything is displayed correctly, but they are not when the text of the Release Note Comments field is displayed by the jiraissues macro. I tried setting the width in different ways and nothing seems to solve that problem.

Second, I cannot get the macro to show the 'fixfor' versions when there are more than one. I tried with "fixVersion", "fixVersions" and "fixfor", but I cannot get it to work.

Unfortunately, I don't think you can fix your first issue without modifying the Jira Macros plugin source. I believe the only field set up to wrap is the description field. (Perhaps a future feature could make wrapping of custom fields more customizable.)

For your second issue, using "fixVersion" should work, though there have been some related bugs, such as CONFJIRA-184. You might try updating your Jira Macros Plugin to the latest version compatible with Confluence 3.2. If that doesn't work, you should open a support request.

I have a page with the jiraissue macro included, it works well when I visit the page as authenticated user (same account in Confluence 3.1 and Jira 4.1.1). When I visit the page without login (anonymous) the I will get an error message: Error formatting macro: jiraissues: java.lang.RuntimeException: Bad Request

Any Idea how to resolve this?

This error message can be accepted, but it create tremendous exception entries in the log file. The log file is blown up when someone create an RSS feed setup which strive this page. The RSS is anonymous and triggers jira every minute....
Thanks for help.

I have the same problem ﻿@Wallabee described. Searched the internet for answers but none were to be found. I have my confluence server as a Truested Applications in JIRA, use the same usernames in both installations. I have verified the jiraissues macro is setup correctly (by using it to read Atlassian's public JIRA site). My macro is setup us:

I have a question, can this Jira macro and Confluence not suck? wiki markup = fail.

Just to get these columns to be fully expanded seems to be impossible. First of all why can't the descriptions column expand or any column expand to fit the actual width of the macro? Second, why is it set to be minimized every time the page or macro is loaded (see pic 2)? Having to constantly expand the height of this thing is a real annoyance. Yes I know I can set a height, setting a fixed height or width is stupid because with some instances there maybe 20 fields and other times 1 or 2. Turning renderMode to static solved a couple of those issues but now I'm getting requests to make it sortable again. If it's dynamic, make it DYNAMIC. Fit widths, columns and expand the view.

Hallo Noah
I'm sorry to hear you're frustrated. Unfortunately, adding a comment to the documentation is unlikely to get the problem fixed. To communicate with our development team and product managers, please would you add an issue to our issue tracker at http://jira.atlassian.com.
Cheers, Sarah

Anonymous

If you receive java.lang.RuntimeException: Not Found error this is may be beacause you are using port redirection with firewall and both jira and confluence are on the same machine.

Port redirection may not work correct when trying to access url from localhost.

Workaround is to add original port number in urls.

For example, if your jira instance is accessible for users via url: http://jira.myhost.com, and this location is transparently mapped via firewall to http://jira.myhost.com:8080 you should use second url form in jiraissues macro for it to work correctly.

Anonymous

Hi everyone,

Quick question, but first here's some background: One of Confluence 3.5's largest improvements is its ability to integrate with Jira. However, if you have a project key with alphanumeric characters, "Insert" does not work with Recently Viewed Jira issues. After you save or preview the insert, a macro error message pops up. I've run multiple tests to make sure that the alphanumeric characters are the issue. I have found that if there is a number ANYWHERE in a Jira project key, Confluence will produce in error message when trying to display this project's issues. Has anyone had this problem?

I am using the Jira issues macro and love it, but was wondering if there is a way to add a row number to the table (other than explicitly defining a # in the Jira issues). We use GHRank ordering, but the numbers don't start with 1 and aren't in order - I need my issues view to be numbered 1-n

Windows Server 2008 R2, Conf 3.5.4, Jira 4.3.4 (two instances of Tomcat on same server), Application links appear correctly configured for trusted apps. The issues list displays correctly in flexigrid in Confluence.
However, the title row for the macro flexigrid displays a url instead of the title.

the code that actually appears in the title row is this:

In other words, everything seems to be working properly except the title row doesnt seem to be properly parsing the title.
The correct title should be "JIRA issues", as shown appended to the URL.
I vaguely recall seeing this problem before, but cant find it in my records ....any tips would be really appreciated.

Anonymous

I am attempting to display a list of the "New Features" in our next release in confluence. We are creating a wiki page within confluence for each new feature to detail requirements, and attach assets. I added a custom field in JIRA that I put in the link to the confluence page. JIRA is picking up the fact that it is a link, so I can click on it, and get to the page, but when I display the list of issues in confluence using the macro, it shows the <a href="link"> tag, instead of providing a link.

Is there any way to have the link I enter in JIRA show up as a link within confluence?

Anonymous

Anonymous

I used the jiraissues macro to create an issues table on my project wiki page. The table is created but only the first field is populated the remaining fields are empty. If I click on the first field it takes me to the issue. We have Jira Studio.

how am I supposed to pass parameter on JIRA 4.0 ? As I have no more access to the macro code ({jiraissues:...}), I would have expected the macro wizard to allow me to input those parameters... is this something that has been forgotten or am I missing something ?

thank's.

Nicolas.

------> my mistake, I was using the jiraissue and not the jiraissues...

Anonymous

Greetings.

I am a fairly new Confluence user, however I have been using the Jiraissues macro for some time. With the Confluence upgrade, a text field I display in my Jira query has embedded html <br> tags which causes the text to not wrap and be displayed as one huge long line. The custom field I am using is a simple text box. Are there any ideas on where the <br> tags are coming from? BTW, I did view the XML which is copied into my Jiraissues macro and the section of the XML I am concerned with looks like this: (? used to replace original text).

Indeed, it's very strange. Whether it is not possible to receive JIRA issues with summary or any other field containing more than 1 word?It is pretty simple to replicate this issue. The template is the following:

Isn't it possible to get issues containing both "example" and "phrase"?

We use the jira-issues macro inside Confluence 4.1.5 and want to display a custom field named 'scope' (data type 'textfield'). The data is being retrieved from JIRA, but unfortunately the custom field's content is wrapped in paragraphs (<p>) and jira-issues writes the content as-is.

This is what we get in the XML-response. Note the wrapped customfieldvalue (<p>Access Management</p>).

Anonymous

Rendering HTML from JIRA

Formatted fields from JIRA can be displayed in Confluence if you set up a Confluence-to-JIRA Trust as described above. Otherwise, such formatted fields will be escaped within the JIRA issues macro output. This is to prevent the possibility of malicious HTML being served by an untrusted JIRA server. The most likely field where you will notice this is in the description field.

So, for example, without the trust relationship, a description column that rendered in JIRA like this -

Description

This is

the description

of my issue

- would actually appear in the JIRA issues macro like this -

Description

<p>This is<ul><li>the description</li><li>of my issue</li></ul></p>

Configuring Confluence-to-JIRA Trust as described above will enable the field to be rendered as expected.

The macro works for us (we had to establish trusted applications between Jira and Confluence with a certificate), but only the "key" column is populated. I want to display status, summary, component, but that does not seem to work. Ideas?

I have successfully configured this plugin, but I would now like to disable the links from the JIRA issues displayed.

My company does not want the clients to be able to jump from the Confluence pages into our JIRA. They should simply be able to see the summary of their Jira issues along with their current status, and that's all.

Is there any way at all to do this? In principle, as far as I can see, this is not functionality built in to the plugin. But could there be another way of disabling the links, via some other confluence configuration ability?

Thanks a lot for any help - yes, I am close to feeling desperate about this...

Anonymous

Is it possible to show additional columns of the subtasks of an issue as status, summary? In the JIRA issue navigator there is only the subtask column shown with the key of the subtask. If I use the VIEWS Menu on the issue navigator in JIRA I can see additional subtask columns.Is there a way to show these columns by using the JIRA Issues Macro in Confluence? Thanks in advance for answers.

I have created a table for my JIRA tickets on my confluence page with customised columns.

if I add the columns "Assignee, Reporter" the syntax for the result is "firstname lastname" , when I add the column participant it is the username (in our case the email address). Even if on the JIRA ticket itself the Participants are shown as "firstname lastname".

Any idea how I can get the Participants displayed in the same way ?

And another question - How I get two participants layouted with a line break, that they are not listed in one line ?

The Participants custom field from JIRA Toolkit renders its value in XML as just the userid with getName, but in the view issue template it uses displayName. I suggest filing an improvement request with the JIRA Toolkit project at https://studio.plugins.atlassian.com/browse/JTOOL

When compiling my release notes in Confluence I need to use the following fields from JIRA: Key, Component/s, (a custom field called) Release note info and Priority. I use the JIRA issues macro to import these items but when I set the Render Mode to static the Component/s and Priority fields are no longer displayed in my list. When I set the render mode back to dynamic these values are displayed again. I need to use the static mode for auditing purposes however. Does anyone have a workaround for this please? At the moment I export the JIRA list to Excel and then copy and paste in Confluence which is not a very productive solution.

Anonymous

My old JIRA Issues Macro don't work on the pages after our company upgraded to confluence 5.1. Any ideas how to fix it? And if I try to setup a new JIRA Macros, it doesn't show me the list of issues from which I see while obtaining the URL of the XML view of a search result. How can I fix it?

Anonymous

Hi there,

I have one question. Is there any possibility to display any values from issue links in Jira Issue Macro? I mean I have a list of projects I want to display in Confluence page but I need to display wiki links from issue links in this list as well. Any suggests? It would be very helpfull for me.

Anonymous

For some reason, the JIRA Issues Macro seems to display differently now than when I used it a week ago. My users love the old layout of the table generated by the JIRA issues macro, which looked something like this:

The above format was great because you could specify the size of the JIRA Issues Macros Table, move columns around, etc. The new version of the macro doesn't seem to allow any of this and is just a static table - which is very frustrating.

Do you know how I can get the JIRA Issues Macro to display my JIRA issues like in the table (screenshot) above?

Indeed we changed the default display mode to static. Even though the UI does't provide the option to switch to dynamic mode you can still do it via insert wiki markup dialog. I.e. Insert -> Wiki Markup and then you can use all the parameters that are not available through the UI. To have dynamic mode you will need to have renderMode=dynamic parameter:

Let me quickly explain why we have chosen this approach and ask for your feedback.

We had 2 different macros for integration with JIRA and for doing very similar things - inserting one issue and inserting multiple issues.

We have unified the experience and tried to simplify the available options.

With the recent changes to Confluence's design the dynamic mode looked out of place and we wanted to de-emphasise it.

For most of the use-cases that we encountered the options that we are providing via UI are enough : people usually want to see the list of issues and adjust what columns they see - the list is usually short enough and if it is long people prefer to view it in JIRA.

Obviously some of the options are not available from UI any more and it is affecting you. Can you please give us a bit more details how you guys usually use the macro so that we can improve it.

We used the JIRA Issues Macro for all our release documentation. I used the following columns when drafting my release notes for example: Key, Components, (a custom added column called) Release Notes Info, Priority and Status.

At first we thought that Rendermode=static will display the JIRA info in a "read-only" manner, i.e. will not be updated dynamically as the content in JIRA changes.

After drafting my release notes in Confluence someone might go and change the status of an issue from resolved to close in JIRA which will make it disappear from the “bugs resolved” list in the release notes. I know that is part of the JIRA/Confluence integration and what makes it great, but we would absolutely love a way to capture a list of JIRA issues in a document and have it remain static, say for instance a snapshot of the known issues for a specific release. What happens now is that the list of known issues changes as they are resolved in JIRA and as a result our documents are not adequate for auditing purposes as we need a document that remains unchanged.

We have tried exporting the documents to PDF and saved this as a link in Confluence, but this defeats the purpose of having “online documentation”. Lately we have been exporting the issues in JIRA to Excel and copy and paste the content into Confluence not using the macro at all, which is a shame as it is an amazing tool and one of the main reasons we bought the system. A solution or option to display a snapshot of unchanged issues would be absolutely awesome!

Great! We are currently working to cover the usecase that you describe. Something that will help you to capture a list of issues for a release or a sprint in a state those issues were at the time of creating the page. The workflow we have in mind is this:

You choose to create a JIRA changelog (we call such a static report a changelog). It is done via Create > JIRA changelog report .

You can specify a project and a version to generate the report for OR alternatively you can specify a JQL query that would return the list of issues you want to embed in a page

Confluence will automatically retrieve the list of issues from JIRA and will embed them into the page. They will be embedded as a text(and links) and will be just a part of the page content. You can delete some of them when editing a page or edit text in any other way.

as we use the macro for kind of a similar use case Marisa does - cross-project release notes covering fields: project, priority, (issue) type, key, fixversion, (a custom date field called) released on live, summary - I am curious if your sentence

"You can specify a project and a version to generate the report for OR alternatively you can specify a JQL query that would return the list of issues you want to embed in a page"

does really mean, that we can show/track issues cross-project wide? As there is still no real cross-project fixversion, we rely in a high degree upon such a solution.

In our team meetings we discuss each new issue for the week in order to add some internal metrics. We wish to include in the meeting minutes a table of these JIRA issues as they stood at the time of the meeting (a snapshot) but still be able to have the ability to follow the JIRA links within the Meeting Minutes. We have a similar problem with Action Item Lists as well in the fact that they are live and hence will change over time when we wish them to remain static for the purposes of the minutes.

Is there a time frame for the release of the above or a method you can suggest for us to be able to achieve this?

It is concerning when Atlassian makes changes and then asks for feedback afterwards. Removing the dynamic option is of great concern because we use the macro in hundreds of places throughout our instance as it allows users to drill through to the issue they want. Static mode doesn't allow drill through.

Even in your own release notes and much of your own documentation, you display the issues in a dynamic mode and it's helpful to drill through to see the details as you often don't want to display all the fields on the page. We use the expand macro to put the issues macro in so that users quickly get to defined filter lists and each list, usually by space, has a customized list of fields that display because each space tracks different issue types. For example, in HR, we list the employees with phone, office number, title, manager, etc as Employee is in an issue type; in sales, we track MRR, products, sales engineer as issue type is a lead, and so on.

I'm not certain what perceived value, outside of minimizing properties to support that were supported, of taking this option away.

What I hear you saying is that I will have to locate the hundreds of places where we use this macro and add the wiki markup to each to get them to render dynamically - true? If true, and you have basically taken this away as it is no longer the default (btw...dynamic was the default...so, to revert to only static by default seems contrary to what you thought before), are you providing users ways to easily migrate all of their macro references to keep them the same?

Thanks for voicing your concerns. I am trying to understand what features you are lacking in the static mode. You mentioned that you customise the list of fields that get displayed - this feature is available in the new UI, you can configure what fields to show. Also you can drill down into any of the issues and see them in full in JIRA.

Things that are only available in dynamic mode are pagination and ability to sort the columns. The rational for not having those features in the static mode is that they are useful only when the list of issues is long. And if the list is long it is much easier to view it in JIRA itself by following the "123 more issues" link at the bottom of the macro.

Anonymous

Hi Anatoli,

Just wanted to follow-up on your question on why we prefer dynamic mode. That mode offers the ability to support pagination, allows users to move columns, etc. - which are just nice features to have from an end user perspective.

The specific use case is that we display Greenhopper tickets within tables in Confluence generated by JIRA Issue Macro tables. This is *huge* for our less-sophisticated users who have trouble wading through the greenhopper sprints, swimlanes, etc - all of which is just way too complex for them. Presenting these Greenhopper Project-Epic tickets in tables in Confluence generated by the macro makes it super simple and to-the-point for these users. Bottom line: It's awesome. They love it. Having the dynamic tables just makes this more flexible.

My suggestion is that you re-release the Macro with the radio-button option to make it static or dynamic, and let customers decide what works best for them. The old Macro parameter form was really easy-to-use and very clear on how to fill it out. The new form (which just generates a static table) only has a few parameters that you can change - something which put me into a panic b/c I thought I had lost all that dynamic table functionality (btw, that's a thinly veiled super-duper thank you to you for helping me bring back the dynamic tables to our instance of Confluence! ).

Final question >>> Do you know if there is any way to custom-set the width of columns of the dynamic table generated by the JIRA Issue Macro? That would be awesome functionality, as many times the column width is too wide. (Note: I am not inquiring about setting the width of the entire table; rather, I want to set the cusom width of individual columns of the table.)

It is interesting to learn how you use the Confluence to JIRA integration to show the progress of epics/sprints to less sophisticated users. We are currently thinking about how to make such integration easier (not necessary with JIRA issues macro) and doing customer interviews. Do you mind talking to us about your needs? Mail me directly (my_first_name@atlassian.com)

Do you know if there is any way to custom-set the width of columns of the dynamic table generated by the JIRA Issue Macro?

My apologies on static mode - I thought that we were able to drill through - but we can, as you mention.

I also concur with Dan, though, on pagination and sorting. We do utilize this macro for display some large lists (e.g. all employees). When the list displays in full on one page, you can imagine, it would be quite long. And depending upon what you are looking for, sorting by name, organization, start date, and manager is important. We also can have longer lists from a products standpoint - e.g. we have filters that pull together all production bugs for each product to make it easier for those troubleshooting, a list of the known issues - again, ability to sort by product, version, component is important.

Having the option to create a JIRA issues table that is dynamic from the UI is pretty critical for us. We're in the middle of deploying Confluence & JIRA & are using a confluence page to create meeting agendas. One section of the agenda will be used for previous meeting actions & having a static table would mean that the issue status would not be correct when we have the meeting.

Our JIRA & confluence users are not capable of create the JIRA issue table using the wiki markup script. How difficult would it be to add the renderMode=Dynamic to the macro UI?

Hans-Peter, you are correct. I appear to have more of an issue with the caching of the issues. However IIRC, the dynamic table has a refresh button that allows users to update the issues at will. If I could have the refresh button, I would be happy.

It's interesting to read this "workaround" provided by an Atlassian employee,

suggesting to use WIKI MARKUP language which (besides of this macro) Atlassian has dropped (in opposition to more than 50% of their customer base).

Anatoli gives a great example here why it was a mistake to remove the Wiki Markup language.

It's also horrible that Atlassian again removes a feature (at least from the parameter editor) without discussing it with the customers first. It appears Atlassian has a very poor understanding of customer needs.

And of course, the suggested workaround is horrible, both from a customer's perspective and from an Atlassian marketing perspective (as you suggest the wiki markup language in contrary to the official Atlassian statements)

Hey Hans, Nice to hear from you. My apologies for the workaround, we are trying to find a way to make sure we aren't blocking your work whilst we address the issues. I understand it's not the cleanest solution, but we are trying to move forward and as I mentioned in my comment below, we are working on addressing these issues.

Anonymous

For some reason, there doesn't seem to be an option to select for a "dynamic" style parameter in the display options above. I think when I had previously inserted the macro, it provided a different configuration box than the one above. I am not quite sure wny it is displaying this new box with fewer options.

Do you know how I can fix this? Maybe there is another macro I should choose in the Macro Browser from the "Insert Other Macros" option in Confluence?

When you click edit on the macro, on the right hand side of the properties that you can input (such as columns), scroll down and you'll see the options of Static and Dynamic.

We are using the most current JIRA version and have the same options as before for the issues macro. We can input the columns as before, put in a title, etc. Can you add a screenshot of what it looks like now when you display? Also, include the name of the macro you are selecting.

the screenshot you show is from a very new version of the JIRA issues macro. I wasn't aware of it being released yet but I'm no expert. I'll raise this to Anatoli Kazatchkov [Atlassian] who is the development manager of this feature - he can probably assist further.

With the latest enhancement to the widget interface we have lost the ability to update the display options when the issue count is "0". We use this count within our dashboards to see how we are tracking within a project and setup the filters for each using our project standards, so at the beginning of the project the counts will all be "0". How can we get around this and display the count as 0? - Thank you!

Thanks for the feedback. This is definitely the usecase we will address next - several people mentioned it. As a workaround for now you can insert the macro via wiki mark up with the right url and count parameter set to true: I.e. Insert -> Wiki Markup :

Yesterday, I installed the new JIRA 5.0 macro and we ran into major performance in our production system, pages with alot of JIRA issues would timeout and fail to load, etc. Than i uninstall 5.0 and reinstalled the older 4.x version, now the "insert JIRA Issue" menu item is missing from the "INSERT" menu. Any ideas on how to resolve that and is Atlassian aware of a performance issue with the new 5.0 code?

..now the "insert JIRA Issue" menu item is missing from the "INSERT" menu. Any ideas on how to resolve that

Please make sure that Applicaton Link is configured, it's under Confluence Admin (<URL>/admin/listapplicationlinks.action). We used to only show this menu if application link was configured.

is Atlassian aware of a performance issue with the new 5.0 code?

We are not aware of any particular problems - the performance should be the same as before. One difference that might be impacting you is the way the static mode (new default mode) is different from dynamic(used to be default). In dynamic mode we draw the table and then asynchronously request the list of the issues from the server again. In static mode the list of issues is retrieved synchronously when the page is generated. Retrieving issues is taking as much time as before but because it is synchronous the page rendering times out.

I can see how it will be impacting you. As a workaround you can increase page rendering timeout:

You'll need to configure application link between Confluence and JIRA; you can do it under Confluence Admin -> Application Links. With the applink configured, you would get extra functionality that otherwise is not available

creating jira issues

pasting JIRA url in editor and having it automatically changed to a macro (URL for single issues or the list of issues)

link from jira-to-confluence (if 2 ways link is configured)

listing recently viewed issues in confluence

If you are not a confluence administrator and if you have to wait until the admin configures it you can use wiki markup to insert the macro - this way it would execute the query as an anonymous user.

I have asked my german speaking colleague what the dialog that you posted actually says and my initial assumption of what it says was wrong. Can you give a bit more details on how you get this dialog? What are you editing?

when i insert the issue macro on an empty page over Insert -> JIRA Issue, than the dialog appears.

After updating the macro-plugin, the application couldn't activate it. And than i activated it manually and this dialog appears. We have some custom HTML in our Confluence-sites, to fix the new chrome-scroll-bug:

Anonymous

It seems that with all of the comments regarding the issues associated with the new and 'reduced' feature macro and the use cases that support why they were using it as before, it seems in the best interest of Atlassian users if Atlassian would provide the dynamic mode and prior features.

It is disappointing that Atlassian keeps changing features by removing functionality BEFORE asking how and why users are utilizing the features that they provide.

If a page takes so long that it generally times out - sure, you can increase the timeout feature. But, do you really want your users to wait that long for their information to render? Why would you not think that column sorting is not important to help users locate issues? Why would you not think that seeing '0' if important to users? Often when nothing displays, the immediate reaction is something is broken - but 0 is a valid count. Why would you not think that users might have lists longer than 20 or 25 - remember, JIRA is not JUST a bug track; it is often used for other activities like project implementations that can have many tasks/subtasks, often displayed to summarize a project - there are other use cases mentioned above, such as employee lists and sprint scope, that will list a long set of issues.

So, you provide a workaround - to now allow users to go back and meet their needs. Inserting wiki markup (when you really have taken it away and users are not in the habit of utilizing it anymore because of your changes) is the only option and it will not be intuitive for the users. How do you expect them to remember all of these wiki markup workarounds you implement because you have taken away functionality? Now, since you have done it, what help are you giving your users to update ALL of their existing space pages where this has been implemented so that you don't increase the support burden on all of your Atlassian administrators?

I've never, EVER worked with a company that their goal seems to be to take away features, deferring their customers to other paid plugins to support what they need and lots and lots of workaround with their older implementation as well as deciding that all of their customers must follow the same processes that Atlassian does, taking away any options that administrators and users should be able to have - to have the options that fit their processes...not be forced to do everything Atlassian's way.

Forcing people out of their own processes is a great way to force customers out of your customer base.

Anonymous

I would concur with proposed order because performance issues makes it unusable.

But, pagination was important to us because we don't want a page that displays 100+ issues and consumes so much real estate, even in an expand macro. It makes it difficult to review.

I would also add the ability to migrate all existing macros to this new one if additional 'code' is required or if existing macros break with this update.

it seems quite odd - you develop a macro that doesn't have the same functionality as before, which results in significant dissatisfaction and then have to 'fix' it to put what was taken out back in. Which JIRA issue was this that made it such a critical priority to refactor and what was the issue being solved? It is difficult to comprehend how this refactoring was of greater value or priority than many existing Confluence bugs with the RTE, PDF exporter, attachment indexing, etc.

if Atlassian uses a well formulated SQL statement performance would be not an issue when pagination is on.

All SQL languages I know allow to limit the number of search results and to skip over a certain number of results (as given by the current page number). Using this, there would be no performance problem and no need to drop functionality.

I everyone, thank you for the feedback on the most recent set of changes to the JIRA issues macro. Just to close off the loop on a lot of the items raised, we have issues raised for the things mentioned on this page. Please watch/vote/comment to stay updated on these issues here:

CONF-30117
-
It is not possible to insert a single JIRA issue or a empty JIRA issue search as a table with the new JIRA issues macro Resolved

CONF-30116
-
Ability to configure the maximum number of issues displayed in the JIRA issues macroResolved

CONF-30115
-
JIRA issues macro times out pages with lots of issuesResolved

We will update these issues as we make progress on them and have started working on some of them. If there is anything that is missing out of here, please feel free to raise it directly on jira.atlassian.com.

Anonymous

There is a significant problem with the JIRA Issue Macro that has persisted for years:

"Custom fields" will not word wrap in the column of a dynamic table created from the JIRA Issue Macro.

I repeat this issue has persisted for *years* (just do a search on the term "wrap" on this page and you will see). This is a hugely important thing to me and the company I work for, as the tables are essentially worthless without this fixed because users don't have the patience to stretch out a column to 12 inches to read the entire text of a column. It's silly and makes me/my colleagues look incompetent.

Could you either tell me a solution on how to fix this or please give me a date by when it would be fixed?

Hi DR, I presume this is the issue you are referring to?
CONF-23800
-
Issuelinks and Description column not being auto word wrap during its display in JIRA Issues MacroResolved
if not, can you please report an issue on jira.atlassian.com because I can't find any other reference to something like this. You may want to watch/vote on that issue to stay updated.

Hi DR,Thanks for your feedback.We centralized all the duplicates of this request into
CONF-28378
-
JIRA Issues Macro textwrapping issue in columnsResolved
and we are planning this in our next sprints.We will keep you posted on its progress in the next weeks.The Confluence team.

Anonymous

I got your reply to my inquiry (above) about the textwrapping bug with the JIRA Issue Macro, and to be perfectly honest I am not really happy about it.

I understand from that note (above) that you've consolidated the various JIRA tickets that have mentioned this over the past almost 5 years. However, if the only progress over the past 5 years is to consolidate all the tickets which complain about this bug - that's not really progress in my book. It feels like Atlassian is completely blowing it off.

I would like to see a plan to resolve / schedule towards resolving this issue asap, as your user base deserves that after waiting for 5 years.

The comments field rendering to a counter is interesting, but not very useful. How can I get the actual comments for the JIRA ticket into this macro? I see the comment content in the URL feed but I am unsure of how to program the macro to fetch and display them. I understand it may only show the first or last comment in the ticket, but anything is better than just a number.

I'd do it by installing an add-on that adds a field type that shows the last N comments. And then add the name of that new Last Comments field in the issuetype columns. That particular add-on is from ServiceRocket where I work

Anonymous

I have a couple problems, we recently updated confluence and JIRA and now when I use a search string to insert JIRA issues the table that's displayed is no longer soratable by column. the second problem i'm having is that the issuelinks column is also no longer an actual link its just text.

in the older versions of JIRA and confluence i used to be able to sort by the headers and the issueliinks were actual links. is there a way to get this functionality back?

The rational for not having sorting in the static mode is that they are useful only when the list of issues is long. And if the list is long it is much easier to view it in JIRA itself by following the "123 more issues" link at the bottom of the macro.

However it looks like quite a few people still want the ability to sort so we will look into implementing :
CONF-30114
-
Ability to sort issues in the JIRA issues macro tableResolved

The second issue you mentioned looks like an existing problem:
CONF-27259
-
When using the Issuelinks field column in the JIRA macro, there are no hyperlinks like in the Issue Navigator in JIRAResolved

When trying to select exactly one jira issue with query “key=ABC-1234” it shows the issue in the Insert Jira Issue dialog box. After pressing insert everything still looks fine. But when pressing Preview or saving the page following error is received:

It is difficult to see what's the problem. Can you please upgrade the plugin to the latest version 5.0.3 and see if the problem still happens. If it is still the case please contact support and we will help you out.

When using a query in the jira macro that at the moment returns only one Jira issue it is converted into a key query.

E.g. query put in search box: type = "User Story" AND "Feature(s)" = E1234 ORDER BY key ASC returns exactly one jira issue at the moment. After pressing insert the issue is displayed on the page but when going back to Edit of the macro the query now shows key = ABC-1234 so the original query has for some reason been converted.

And as it is now a key query saving the page ends up in previous error when trying to save the page: Error rendering macro 'jira' : com.atlassian.confluence.macro.MacroExecutionException: java.lang.NullPointerException

Why is the original query converted into a key query? As it will not work after more issues have been added to jira that should match the originally inserted query.

The "images" field is having issue and the content is not coming over as a part of JIRA Macro. All other fields are working fine. Trying to get this working on JIRA 6.3.13 and Confluence 5.5.6. Any idea why the images property is having an issue

I am using JIRA issues Macro. The Prameter window is working well. It is also accepting my JQL and displaying the relevant results. But when i am inserting the data into my confluence page and asaving the page, i am getting an error which says " Cannot render JIRA issues Macro. Execution Error"

We currently cache the information about issues for an hour so the status can lag for at most an hour. We are working on fixing this limitation and the new version of the plugin that doesn't have this limitation should be available in a matter of weeks.

How are you planning to use JIRA dashboard in confluence? Is using JIRA dashboard itself out of the question? We would love to hear your use case and details (might be doing some work in this area in the future).

We are going to build info page for employees in confluence with few KPIs and reports based on JIRA. In confluence we can make one space, adding many pages. In confluence we can add more informations. Employees can comment this pages and so on. In JIRA we will only show something and it's constant, in confluenve the team can create something based on showed infromations. The idea for this page is: one link, all info about your projects you are assigned, involved.

We are still creating the final solution, so this is only a part of our idea. When we finished, we can show our results and tell about expiernce.

Hi Iris, I believe the current version of the JIRA issues macro does not refresh the count without editing the list of issues to show / count. There is a lot of info about this issue here (its not specifically about the issue count, but I suspect the caching issue is the same)
CONF-30077
-
JIRA issue macro aggressively caches, new issues take a while to appear in the issues macro Resolved
. You will see a big improvement in this for Confluence 5.4 (and in the next few weeks for OnDemand customers).

iris blackburn: We will remove cache for total count in version 5.2 of JIRA Issues Macro which is bundled with Confluence 5.4. It means that you will always get refresh total count. It will go to market soon.

Hi Dirk, when creating issues from a table when viewing a page, Confluence will use the text from the column that you highlighted text in to populate the Summary field in JIRA, and then add the created issue to that column once it has been successfully created in JIRA.

It only pulls text from one column, so you would need to add your description manually. Sorry!

As Rachel mentioned you can create issues from a table in bulk, one per row. The functionality currently allows to populate only summary for the each created issue from one column of the table. There is a feature request to map more than just one column to other fields of JIRA issues:
CONF-31867
-
Ability to map more fields from a Confluence table into a JIRA issue when highlighting and creating issuesOpen
?

If you want to customise the display, choose Display options and adjust the columns and number of issues that will appear in your table of issues.

If I try to adjust the number of issues, I cannot do that because the field Maximum Issues is missing in the settings of the JIRA Issues Macro. Does anybody have an idea, how I could fix that? Confluence is just displaying 20 issues, but I would like to show all matching (24 at the moment).

Anonymous

We just upgraded (for testing purposes) to 5.0 version and the display option is not available. This was the latest version available for our Confluence install of 5.1.5. When was this display option introduced as we cannot upgrade without it. We also cannot upgrade our Confluence install to the latest version because Adaptavist doesn't have compatible macros as of yet.

Having upgraded to Confluence 5.2.5 and JIRA Macros 5.1.3, I am unable to specify a title for new instances of the macro where the results are displayed in table form; however, existing macro instances that have a title defined still display it. I've been unable to find anything to explain this change in behaviour - is this a bug or a feature change? The ability to set a title is crucial as it not only describes the nature of the data, but also provides a link to that filter in the target JIRA instance. (My Confluence and JIRA instances are connected via an Application Link.)

[Hi Paul, we no longer support title for JIRA Issues Macro, you can use normal HTML markup as its title. For link to the corresponding JIRA instance, you can either use the link at the bottom of issue table or insert an issue count.

Hi Nguyen, thanks for your prompt response. Is this change documented or explained anywhere? As I say, I was unable to find anything when researching this. And surely this page needs to be updated accordingly too, as it clearly states "(Title) You can customise the title text at the top of the JIRA issues table with this parameter."

Hi Paul, sorry this change was not reflected in the docs. It was an oversight on my part. The docs have now been updated. As Nguyen points out, there is a link at the bottom of the macro that will link to the filter or query in JIRA, which I hope will be able to serve the same purpose as your customised title.