Page MenuHomePhabricator

Support "JIRA Issue URIs" as a Herald field for revisions
ClosedPublic

Authored by epriestley on Apr 10 2019, 4:14 PM.
Tags
None
Referenced Files
F19931823: D20386.diff
Fri, Apr 10, 5:08 AM
F19877675: D20386.diff
Mon, Mar 16, 5:50 PM
F18738054: D20386.id48649.diff
Oct 1 2025, 1:53 PM
F18735628: D20386.id48653.diff
Oct 1 2025, 2:36 AM
F18629931: D20386.diff
Sep 16 2025, 10:18 AM
F18518690: D20386.diff
Sep 5 2025, 3:34 PM
F18468133: D20386.diff
Sep 2 2025, 2:27 PM
F18105766: D20386.id.diff
Aug 10 2025, 7:32 PM
Subscribers
None

Details

Summary

See PHI1175. An install would like to trigger some reminders/guidance if users don't link revisions to JIRA issues.

Expose "JIRA Issue URIs" as a field so Herald can act on the presence or absence of issues.

I'm exposing "JIRA Issue URIs", not a field like "[ Has Jira Issue ][ is true ]", since it's a bit more flexible: you can use a regexp to test against particular PROJ-123 project prefixes in JIRA, for example.

Test Plan

jira-issue-uris.png (1×1 px, 225 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Apr 10 2019, 5:32 PM
src/applications/differential/herald/DifferentialRevisionJIRAIssueURIsHeraldField.php
28

(This edge is kind of named backwards, but this is the correct half of it to query for.)

This revision was automatically updated to reflect the committed changes.