Concourse & Jira DC Portal

1. Business Objectives and Outcomes

Put Simply
Authorized project users can update many existing Jira work items from a CSV in the selected project, after mapping and validating changes, without an admin ticket.

Problem / Opportunity
Project teams frequently need the same field change across many work items. Doing that one issue at a time, or waiting on an administrator, slows delivery and increases the chance of updates landing in the wrong project or on the wrong items.

Why This Matters
Bulk update is a high-demand self-service utility. A mandatory validate step protects Jira data quality while still removing the admin bottleneck.

Feature Objectives & Measures of Success

• Users with the approved bulk-update capability can start the flow only after a project is selected.

• Users can upload a CSV and specify delimiter and date or date-time formats.

• Users must map a work-item key column and source columns to Jira fields.

• Users can preview current versus proposed values for the selected project before any update.

• The portal validates keys, project membership, permissions, field types, dates, and existing dropdown values before updating.

• Users can resolve blocking errors or, only if Product approves a partial-update policy, knowingly continue for eligible rows.

• Execution provides progress, safe retry behavior, a downloadable result report, and an audit trail.