Making your own Activity Streams Provider


  • Activity Streams 4.1 and later.
  • JIRA 4.4 and later.
  • Confluence 4.0 and later.

Level of experience:

Intermediate. Our tutorials are classified as 'beginner', 'intermediate' and 'advanced'. This one is at 'intermediate' level. If you have never developed a plugin before, you may find this one a bit difficult.

Time to Complete:

1 hour

On this page:


Atlassian Activity Streams displays 'activities', which are items that represent recently occurring events. Example events are the creation of a Crucible review or the transition of a JIRA issue. The stream is created from the input of 'providers' that create sets of items. This screenshot shows what part of an activity stream looks like, displayed within a JIRA gadget:

In the image, the review activity is created by a FishEye/Crucible provider and the items for issue creation and issue linking are created by a JIRA provider. These particular providers are included in the Activity Streams project, but providers do not have to be included in the project. External providers allow you to inject custom events into your activity streams. You can see an example external provider plugin in the external-provider-sample project on Bitbucket. Since external providers are structured in the same way as internal providers, you can look at the streams-<product-name>-plugin modules in the Activity Streams source for more examples. The FishEye/Crucible and JIRA providers shown above can be found in the Activity Streams source.

Users can filter the items providers create. For example, a user may want to see only items from the user 'admin'. See this screenshot:

The rest of this page shows you what you need to do to make a new provider for Activity Streams.

Plugin Source

We encourage you to work through this tutorial. If you want to skip ahead or check your work when you are done, you can find the plugin source code on Atlassian Bitbucket. Bitbucket serves a public Git repository containing the tutorial's code. To clone the repository, issue the following command:

$ git clone

Alternatively, you can download the source using the get source option here:

Step 1. Set up your plugin project

You can just copy and tweak the sample project, which is already set up to run Activity Streams 5.0 in an early-access milestone of JIRA 5.0. Or you may want to use the Atlassian Plugin SDK to create a plugin skeleton and then, in your sample project's pom.xml, specify a product version containing your desired version of Activity Streams.

Step. 2 Add the skeletons of classes for your provider

The following Activity Streams interfaces (all from package com.atlassian.streams.spi) are provided for you to implement.

This is the required implementation for a plugin that inserts items in Activity Streams:


In the getActivityFeed method, construct your feed out of StreamsEntry items. There is more detail on creating StreamsEntry items below, in the section on making a feed item below.

Optionally, you can add these implementations as needed:


Can provide filtering options that will be displayed to the user in the stream gadget configuration. For example, one filter implemented by the streams-jira-plugin is filtering by issue type (bug, task, etc).


Can check that keys, such as project or space keys, submitted as user filtering options are valid. Can also be used to check permissions, for example that the requested key represents a project the user has permission to see.


Can return a set of valid keys that a user can filter with.


Implement the postReply method to allow responses to your stream items to be made via the streams gadget. For example, the streams-confluence-plugin implements postReply to allow responses to comments or pages to be made via the gadget.

Step 3. Add the activity-provider module to your atlassian-plugin.xml

It looks something like this, with the nested elements being optional based on whether you are using them or not:

    <activity-streams-provider key="external-provider" name="External Provider" i18n-name-key=""
        <filter-provider class="com.atlassian.streams.ExternalFilterOptionProvider" />
        <validator class="com.atlassian.streams.ExternalStreamsValidator" />
        <key-provider class="com.atlassian.streams.ExternalStreamsKeyProvider" />
        <comment-handler class="com.atlassian.streams.ExternalStreamsCommentHandler" />

Step 4. Make a feed item (a StreamsEntry)

In your StreamsActivityProvider.getActivityFeed implementation, you will need to create the entries for the items you want to appear in the stream. The sample plugin does this in ExternalStreamsActivityProvider:

  Click here to expand...
     * Transforms a single {@link AuditLogEntry} to a {@link StreamsEntry}.
     * @param auditLogEntry the log entry
     * @return the transformed streams entry
    private StreamsEntry toStreamsEntry(final AuditLogEntry auditLogEntry)
        final URI fakeUri = URI.create("");

        StreamsEntry.ActivityObject activityObject = new StreamsEntry.ActivityObject(StreamsEntry.ActivityObject.params()

        final UserProfile userProfile = userProfileAccessor.getUserProfile(auditLogEntry.getUsername());

        StreamsEntry.Renderer renderer = new StreamsEntry.Renderer()
            public Html renderTitleAsHtml(StreamsEntry entry)
                String userHtml = (userProfile.getProfilePageUri().isDefined()) ? "<a href=\""+userProfile.getProfilePageUri().get()+"\"  class=\"activity-item-user activity-item-author\">" + userProfile.getUsername() + "</a>" : userProfile.getUsername();
                return new Html(userHtml + " " + auditLogEntry.getTitle(i18nResolver));

            public Option<Html> renderSummaryAsHtml(StreamsEntry entry)
                return Option.none();

            public Option<Html> renderContentAsHtml(StreamsEntry entry)
                return Option.none();

        ActivityVerb verb = ExternalFilterOptionProvider.ExternalUPMActivityVerbs.getVerbFromEntryType(auditLogEntry.getEntryType());

        StreamsEntry streamsEntry = new StreamsEntry(StreamsEntry.params()
                .postedDate(new DateTime(auditLogEntry.getDate()))
                .applicationType(applicationProperties.getDisplayName()), i18nResolver);
        return streamsEntry;

Here are some examples of the renderer implementation that show where method results end up in the gadget.

  Click to see example 1...
new StreamsEntry.Renderer()
    public StreamsEntry.Html renderTitleAsHtml(StreamsEntry entry)
        return new StreamsEntry.Html("title");

    public Option<StreamsEntry.Html> renderSummaryAsHtml(StreamsEntry entry)
        return Option.some(new StreamsEntry.Html("summary"));

    public Option<StreamsEntry.Html> renderContentAsHtml(StreamsEntry entry)
        return Option.some(new StreamsEntry.Html("content"));

  Click to see example 2...
new StreamsEntry.Renderer()
    public StreamsEntry.Html renderTitleAsHtml(StreamsEntry entry)
        return new StreamsEntry.Html("title");

    public Option<StreamsEntry.Html> renderSummaryAsHtml(StreamsEntry entry)
        return Option.none();

    public Option<StreamsEntry.Html> renderContentAsHtml(StreamsEntry entry)
        return Option.some(new StreamsEntry.Html("content"));

Step 5. Run your plugin

Use mvn clean amps:debug -Dproduct=jira in your plugin directory root to run JIRA with your provider plugin installed. Get an activity stream in JIRA by adding it to a dashboard with the "Activity Stream" gadget.
The sample plugin has an activity stream loaded on the default dashboard if you log in as admin (password is also admin).

The sample plugin adds entries from the UPM (Universal Plugin Manager) audit log to the stream, in this case the installation of the Gliffy plugin to help create robot designs:

Additionally, if you specify filters in your implementation of StreamsFilterOptionProvider, you can have your own provider-specific Activity Streams filters. The sample plugin includes filters for various kinds of plugin activity.

Was this page helpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport