actions/update-issue/update-issue.mjs
import { ConfigurationError } from "@pipedream/platform"; import constants from "../../common/constants.mjs"; import utils from "../../common/utils.mjs"; import common from "../common/issue.mjs"; export default { ...common, key: "jira-update-issue", name: "Update Issue", description: "Updates an issue. A transition may be applied and issue properties updated as part of the edit, [See the docs](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-put)", version: "0.2.17", annotations: { destructiveHint: true, openWorldHint: true, readOnlyHint: false, }, type: "action", props: { ...common.props, projectId: { propDefinition: [ common.props.app, "projectID", ({ cloudId }) => ({ cloudId, }), ], }, issueIdOrKey: { reloadProps: true, propDefinition: [ common.props.app, "issueIdOrKey", ({ cloudId }) => ({ cloudId, }), ], }, issueTypeId: { reloadProps: true, propDefinition: [ common.props.app, "issueType", ({ cloudId, projectId, }) => ({ cloudId, projectId, }), ], optional: true, }, notifyUsers: { type: "boolean", label: "Notify Users", description: "Whether a notification email about the issue update is sent to all watchers. To disable the notification, administer Jira or administer project permissions are required. If the user doesn't have the necessary permission the request is ignored.", optional: true, }, overrideScreenSecurity: { type: "boolean", label: "Override Screen Security", description: "Whether screen security should be overridden to enable hidden fields to be edited. Available to Connect app users with admin permissions.", optional: true, }, overrideEditableFlag: { type: "boolean", label: "Override Editable Flag", description: "Whether screen security should be overridden to enable uneditable fields to be edited. Available to Connect app users with admin permissions.", optional: true, }, transitionId: { label: "Transition ID", description: "The ID of the issue transition. Retrieving options requires a static `issueIdOrKey`. Required when specifying a transition to undertake.", propDefinition: [ common.props.app, "transition", ({ cloudId, issueIdOrKey, }) => ({ cloudId, issueIdOrKey, }), ], }, transitionLooped: { type: "boolean", label: "Transition Looped", description: "Whether the transition is looped.", optional: true, }, }, async additionalProps() { const { cloudId, projectId, issueTypeId, issueIdOrKey, } = this; try { const { fields } = await this.app.getEditIssueMetadata({ cloudId, issueIdOrKey, }); return this.getDynamicFields({ fields, }); } catch { if (!issueTypeId) { throw new ConfigurationError("Please enter `projectId` and `IssueTypeId` to retrieve additional props."); } const { projects: [ { issuetypes: [ { fields = {} } = {}, ], }, ], } = await this.app.getCreateIssueMetadata({ cloudId, params: { projectIds: projectId, issuetypeIds: issueTypeId, expand: "projects.issuetypes.fields", }, }); const keys = [ constants.FIELD_KEY.ISSUETYPE, constants.FIELD_KEY.PROJECT, ]; return this.getDynamicFields({ fields, predicate: ({ key }) => !keys.includes(key), }); } }, async run({ $ }) { const { app, cloudId, issueIdOrKey, projectId, issueTypeId, notifyUsers, overrideScreenSecurity, overrideEditableFlag, historyMetadata, properties, transitionId, transitionLooped, update, additionalProperties, ...dynamicFields } = this; const fields = utils.reduceProperties({ additionalProps: this.formatFields(dynamicFields), }); const { transition } = utils.reduceProperties({ additionalProps: { transition: [ transitionId, { id: transitionId, looped: transitionLooped, }, ], }, }); const params = utils.reduceProperties({ additionalProps: { notifyUsers, overrideScreenSecurity, overrideEditableFlag, }, }); await app.updateIssue({ $, cloudId, issueIdOrKey, params, data: { fields, historyMetadata: utils.parseObject(historyMetadata), properties: utils.parse(properties), update: utils.parseObject(update), ...utils.parseObject(additionalProperties), }, transition, }); $.export("$summary", `Issue with ID(or key): ${this.issueIdOrKey} has been updated.`); return { success: true, issueIdOrKey, }; }, };
Chase Roberts@chsrbrts@benedictevans If you haven’t used @pipedream yet, then you haven’t lived.
✨Ellie Day✨@heyelliedayEvaluation update: @pipedream has quite literally been a dream to work with! I’m excited to leverage this tool for all the various workflows I need to write. I’m currently at 11k invocations a day from the initial workflows I’ve written in the past couple weeks.
Michael Braedley@MBraedleyUpdate: I got it working properly, and it's working so well that I'm dropping IFTTT. @pipedream can do everything that IFTTT basic can, and most (if not all things) IFTTT pro can for free or at a reasonable price if you need it. I am recommending it for basically any power user.
Thomas Cutting@mrthomascuttingWant quick+dirty integrations for a serverless workflow - @pipedream is my new go-to 😃
Matthew Roberts@mattdotrobertsday 013 - finally hit node js. This is the secret sauce of taking #nocode projects that one step further. Pumped about getting deeper into @pipedream now
Kenneth Auchenberg 💭@auchenbergYahoo Pipes is back! Kinda 😍 @pipedream
Raymond Camden 🥑@raymondcamdenAwesome video by the @pipedream folks showing real time twitter sentiment analysis integrated with Google Sheets. This is where Pipedream *really* shines, connecting systems together in easy workflows.
Nacho Caballero@nachocaballeroI couldn't recommend @pipedream more. It's an amazing service to integrate different APIs. Much more powerful than Zapier and more user-friendly than AWS Lambda. I'm very proud to wear this t-shirt #NoCode
Jason Snow@jyksnwDeveloped a working prototype environmental sensor IoT solution with @particle Photon, @pipedream, and @MongoDB with full graphing and alerting in less than a day! All amazing technology, will def. be exploring these more.
Steven Terrana@steven_terrana@burgwyn you've inspired me to finally set up my own blog. I'll make sure my first blog post explains the tech behind the setup. think @obsdmd + @GatsbyJS + @pipedream.
🚄 James Augeri, PhD@DotDotJamesWant to low-code your back end, need more horsepower than @Bubble / @KnackHQ, or just miss Yahoo! Pipes? Check out @PipeDream
Sébastien Chopin@AtinuxGitHub issues should be like @linear_app for maintainers. Looking forward more integrations with GH actions or tools like @pipedream 👀
Raul@raul_predescuIf you're a dev and not using @pipedream, you're missing out. Been using it for months, daily. FREE for devs. Plenty of integrations and good limits. Absolutely love it.
Bruno Skvorc@bitfallsSo @pipedream is pretty amazing. In 3 minutes I just made a flow which adds @rickastley's Never Gonna Give You Up to my @spotify playlist whenever a new pull request arrives in an old repo of mine.
Zach Lanich@ZachLanichUm, wow 🤯 @pipedream
Steven Bell@bellontechI just used @pipedream to build a Shopify App. Wow, they make small backed tasks easy.
Jay Hack 🎩🇺🇸@_jayhack_Very impressed with this bad boi - it reminds me of a @PalantirTech internal tool, but geared towards integrations instead of data analysis and far more customizable. Great expectations here 🚀🤩
Tree Sturgeon 🔥🚴♂️🌳@philsturgeonFor context this is day 2 of a really challenging and stupid migration from Notion to @airtable with disparate/missing data. It's going better than expected and thanks to @pipedream I don't have to bother the iOS dev to add W3W.