Create Jira Version in project with Jira API on New Item in Feed from RSS API

Pipedream makes it easy to connect APIs for Jira, RSS and 2,400+ other apps remarkably fast.

Trigger workflow on

New Item in Feed from the RSS API

Next, do this

Create Jira Version in project with the Jira API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a RSS trigger and Jira action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Item in Feed trigger
1. Connect your RSS account
2. Configure timer
3. Configure Feed URL
4. Configure Published After
Configure the Create Jira Version in project action
1. Connect your Jira account
2. Select a Cloud ID
3. Select a Project ID
4. Configure Version name
5. Optional- Configure Description
6. Optional- Configure Archived
7. Optional- Configure Released
8. Optional- Configure Start date
9. Optional- Configure Release date
10. Optional- Configure Move unfixed issues to
11. Optional- Configure Expand
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Details#

This integration uses pre-built, source-available components from Pipedream's GitHub repo. These components are developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

Trigger#

New Item in Feed on RSS

Description:Emit new items from an RSS feed

Version:1.2.7

Key:rss-new-item-in-feed

View on GitHub

RSS Overview#

The RSS app allows users to automatically fetch and parse updates from web feeds. This functionality is pivotal for staying abreast of content changes or updates from websites, blogs, and news outlets that offer RSS feeds. With Pipedream, you can harness the RSS API to trigger workflows that enable a broad range of automations, like content aggregation, monitoring for specific keywords, notifications, and data synchronization across platforms.

Trigger Code#

import { defineSource } from "@pipedream/types";
import rss from "../../app/rss.app.mjs";
import rssCommon from "../common/common.mjs";
export default defineSource({
    ...rssCommon,
    key: "rss-new-item-in-feed",
    name: "New Item in Feed",
    description: "Emit new items from an RSS feed",
    version: "1.2.7",
    type: "source",
    dedupe: "unique",
    props: {
        ...rssCommon.props,
        url: {
            propDefinition: [
                rss,
                "url",
            ],
        },
        publishedAfter: {
            type: "string",
            label: "Published After",
            description: "Emit items published after the specified date in ISO 8601 format .e.g `2022-12-07T12:57:10+07:00`",
            default: new Date(Date.now() - 24 * 60 * 60 * 1000).toISOString(), // default to one day ago
        },
    },
    hooks: {
        async activate() {
            // Try to parse the feed one time to confirm we can fetch and parse.
            // The code will throw any errors to the user.
            await this.rss.fetchAndParseFeed(this.url);
        },
    },
    methods: {
        ...rssCommon.methods,
        generateMeta: function (item) {
            return {
                id: this.rss.itemKey(item),
                summary: item.title,
                ts: Date.now(),
            };
        },
    },
    async run() {
        const items = await this.rss.fetchAndParseFeed(this.url);
        for (const item of items.reverse()) {
            const publishedAfter = +new Date(this.publishedAfter);
            const ts = this.rss.itemTs(item);
            if (Number.isNaN(publishedAfter) || publishedAfter > ts) {
                continue;
            }
            const meta = this.generateMeta(item);
            this.$emit(item, meta);
        }
    },
});

Trigger Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.

Label	Prop	Type	Description
RSS	`rss`	`app`	This component uses the RSS app.
	`timer`	`$.interface.timer`	How often you want to poll the feed for new items
Feed URL	`url`	`string`	Enter the URL for any public RSS feed
Published After	`publishedAfter`	`string`	Emit items published after the specified date in ISO 8601 format .e.g `2022-12-07T12:57:10+07:00`

Trigger Authentication#

The RSS API does not require authentication.

About RSS#

Real Simple Syndication

Action#

Create Jira Version in project on Jira

Description:Creates a project version., [See the docs](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-project-versions/#api-rest-api-3-version-post)

Version:0.1.9

Key:jira-create-version

View on GitHub

Jira Overview#

The Jira API opens up a world of possibilities for automating project management tasks, syncing with other tools, and enhancing data visibility. With Pipedream's integration, you can streamline issue tracking by automatically creating, updating, and searching for issues in Jira, as well as managing projects, sprints, users, and more. This integration not only saves time but also ensures real-time data flow across various platforms, keeping teams in sync and projects on track.

Action Code#

import jira from "../../jira.app.mjs";

export default {
  key: "jira-create-version",
  name: "Create Jira Version in project",
  description: "Creates a project version., [See the docs](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-project-versions/#api-rest-api-3-version-post)",
  version: "0.1.9",
  type: "action",
  props: {
    jira,
    cloudId: {
      propDefinition: [
        jira,
        "cloudId",
      ],
    },
    projectID: {
      propDefinition: [
        jira,
        "projectID",
        (c) => ({
          cloudId: c.cloudId,
        }),
      ],
    },
    name: {
      type: "string",
      label: "Version name",
      description: "The unique name of the version. Required when creating a version. The maximum length is 255 characters.",
    },
    description: {
      type: "string",
      label: "Description",
      description: "The description of the version.",
      optional: true,
    },
    archived: {
      type: "boolean",
      label: "Archived",
      description: "Indicates that the version is archived.",
      optional: true,
    },
    released: {
      type: "boolean",
      label: "Released",
      description: "Indicates that the version is released. If the version is released a request to release again is ignored. Not applicable when creating a version.",
      optional: true,
    },
    startDate: {
      type: "string",
      label: "Start date",
      description: "The start date of the version. Expressed in ISO 8601 format (yyyy-mm-dd).",
      optional: true,
    },
    releaseDate: {
      type: "string",
      label: "Release date",
      description: "The release date of the version. Expressed in ISO 8601 format (yyyy-mm-dd).",
      optional: true,
    },
    moveUnfixedIssuesTo: {
      type: "string",
      label: "Move unfixed issues to",
      description: "The URL of the self link to the version to which all unfixed issues are moved when a version is released. Not applicable when creating a version. Optional when updating a version.",
      optional: true,
    },
    expand: {
      propDefinition: [
        jira,
        "expand",
      ],
      description: "Use expand to include additional information about version in the response. This parameter accepts a comma-separated list. Expand options include:\n`operations` Returns the list of operations available for this version.\n`issuesstatus` Returns the count of issues in this version for each of the status categories `to do`, `in progress`, `done`, and `unmapped`.",
    },
  },
  async run({ $ }) {
    const response = await this.jira.createVersion({
      $,
      cloudId: this.cloudId,
      data: {
        projectId: this.projectID,
        name: this.name,
        description: this.description,
        archived: this.archived,
        released: this.released,
        startDate: this.startDate,
        releaseDate: this.releaseDate,
        moveUnfixedIssuesTo: this.moveUnfixedIssuesTo,
        expand: this.expand,
      },
    });
    $.export("$summary", `Version has been created successfuly. (ID:${response.id}, NAME:${response.name})`);
    return response;
  },
};

Action Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI.

Label	Prop	Type	Description
Jira	`jira`	`app`	This component uses the Jira app.
Cloud ID	`cloudId`	`string`	Select a value from the drop down menu.
Project ID	`projectID`	`string`	Select a value from the drop down menu.
Version name	`name`	`string`	The unique name of the version. Required when creating a version. The maximum length is 255 characters.
Description	`description`	`string`	The description of the version.
Archived	`archived`	`boolean`	Indicates that the version is archived.
Released	`released`	`boolean`	Indicates that the version is released. If the version is released a request to release again is ignored. Not applicable when creating a version.
Start date	`startDate`	`string`	The start date of the version. Expressed in ISO 8601 format (yyyy-mm-dd).
Release date	`releaseDate`	`string`	The release date of the version. Expressed in ISO 8601 format (yyyy-mm-dd).
Move unfixed issues to	`moveUnfixedIssuesTo`	`string`	The URL of the self link to the version to which all unfixed issues are moved when a version is released. Not applicable when creating a version. Optional when updating a version.
Expand	`expand`	`string`	Use expand to include additional information about version in the response. This parameter accepts a comma-separated list. Expand options include: `operations` Returns the list of operations available for this version. `issuesstatus` Returns the count of issues in this version for each of the status categories `to do`, `in progress`, `done`, and `unmapped`.

Action Authentication#

Jira uses OAuth authentication. When you connect your Jira account, Pipedream will open a popup window where you can sign into Jira and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any Jira API.

Pipedream requests the following authorization scopes when you connect your account:

read:jira-workmanage:jira-projectread:jira-userwrite:jira-workmanage:jira-data-providerread:meoffline_accessread:issue-details:jiraread:board-scope:jira-softwareread:webhook:jirawrite:webhook:jiraread:field:jiraread:project:jiradelete:webhook:jirawrite:board-scope:jira-softwareread:board-scope.admin:jira-softwareread:sprint:jira-softwarewrite:sprint:jira-softwareread:field.option:jirawrite:field.option:jiraread:custom-field-contextual-configuration:jira write:custom-field-contextual-configuration:jiramanage:jira-configurationread:jql:jira

About Jira#

Jira is the #1 agile project management tool used by teams to plan, track, release, and support great software with confidence

More Ways to Connect Jira + RSS#

Other Popular Integrations#

Merge RSS Feeds with RSS API on New Event from Jira API

Jira + RSS

Create Jira Version in project with Jira API on New Item in Feed from RSS API

Pipedream makes it easy to connect APIs for Jira, RSS and 2,400+ other apps remarkably fast.

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

1-24of2,400+apps by most popular

1
-
24
of
2,400+
apps by most popular