Receiving Search Results as an RSS Feed

JIRA enables you to subscribe to an RSS 2.0 feed that is based on any issue filter (saved search), or on your chosen search results, as displayed in the Issue Navigator.

You can choose either an RSS feed that contains issue data (Summary, Description, etc), or one that contains comments.

Note that the tempMax parameter can be used to control the maximum number of issues that are returned, e.g. sample RSS feed of the latest 15 issues reported on jira.atlassian.com.

Subscribing to an RSS Feed

Before you begin:

  • Tip: If you only want to receive current comments in an RSS feed, use the Date Updated field when doing a search. For example, to only receive comments created in the last week, add the Date Update field and set it to updated within the last 1 week.
  • The tempMax parameter in the RSS URL can be used to control the maximum number of issues returned in your RSS feed.
  • If you are getting an empty RSS feed, make sure you have logged in to JIRA — see Accessing protected data (below).

To subscribe to an RSS feed:

  1. Choose Issues > Search for Issues.
  2. Refine your search, as described in Searching for Issues, then choose the Export menu.
  3. Choose one of the following from the dropdown menu:
    • 'RSS (Issues)' — this will create an RSS feed that contains just issue data.
    • 'RSS (Comments)' — this will create an RSS feed that contains comments. 
  4. Copy the URL that is currently displayed on your Issue Navigator screen.
  5. Paste the URL into your RSS reader.

Here is a sample RSS feed:

Accessing protected data

When accessing data generated from JIRA, you may find that access to some resources requires user authentication (i.e. requires you to login). There are three options for this:

  1. To enable access to data without logging in, your JIRA administrator may specify the 'Browse' permission for Anyone.
  2. You can provide the parameters os_username and os_password in the request URL (e.g. http://jira.atlassian.com/browse/TST-1?os_username=tester&os_password=tstpassword). The problem with this method is that it transmits your username and password across the wire in clear text, which may not be an option for some users.
  3. You can provide the request parameter os_authType=basic (e.g. http://mycompany.com/anypage?os_authType=basic). This will force the server to issue a challenge for user credentials (i.e. a login prompt) via the basic http authentication protocol. If you are running over SSL, you still need to specify the os_authType=basic parameter if you require the user to authenticate.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport