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
F22658976: D20386.id48653.diff
Thu, Oct 1, 7:17 AM
F22658975: D20386.id48649.diff
Thu, Oct 1, 7:17 AM
F22658974: D20386.id.diff
Thu, Oct 1, 7:17 AM
F22656340: D20386.diff
Thu, Oct 1, 3:55 AM
Unknown Object (File)
Jul 4 2026, 9:45 AM
Unknown Object (File)
Jun 26 2026, 11:01 PM
Unknown Object (File)
Jun 21 2026, 1:58 AM
Unknown Object (File)
Apr 10 2026, 5:08 AM
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
Branch
jira1
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 22524
Build 30839: Run Core Tests
Build 30838: arc lint + arc unit

Event Timeline

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

(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.