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
F18105766: D20386.id.diff
Sun, Aug 10, 7:32 PM
F18101969: D20386.diff
Sat, Aug 9, 5:09 PM
F17757715: D20386.diff
Jul 22 2025, 4:25 PM
Unknown Object (File)
May 29 2025, 5:08 PM
Unknown Object (File)
May 28 2025, 3:29 PM
Unknown Object (File)
May 7 2025, 12:52 AM
Unknown Object (File)
Apr 13 2025, 11:36 AM
Unknown Object (File)
Apr 12 2025, 9:01 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.