Documentation for JIRA 4.1. Documentation for other versions of JIRA is available too.

Skip to end of metadata
Go to start of metadata

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

Subscribing to an RSS Feed

To subscribe to an RSS feed,

  1. On the top navigation bar, click the 'Issues' tab.
  2. Refine your search, as described in 'Searching for Issues', until the required results are displayed in the Issue Navigator.
  3. Click the 'Views' menu, and select one of the following:
    • 'RSS (Issues)' — this will create an RSS feed that contains just issue data.
    • 'RSS (Comments)' — this will create an RSS feed that contains comments.
      (tick) HINT: To only receive current comments, use the Updated, Updated After and Updated Before fields in the 'Dates and Times' section of the search form. E.g. to only receive comments created in the last week, type -1w in the From field.
  4. Copy the URL that is currently displayed on your Issue Navigator screen.
    (info) NOTE: The tempMax parameter can be used to control the maximum number of issues returned in your RSS feed.
  5. Paste the URL into your RSS reader.
    (info) NOTE: If you are getting an empty RSS feed, make sure you have logged in to JIRA — see Accessing protected data (below).

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. 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. 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.

Related Topics