Category: Jira Product Discovery — Feature Suggestion
Description:
JPD tracks field change history internally — changes are visible in the History tab of each idea (who changed what, when, old value → new value). However, this history is stored in JPD's own data layer and is not written to Jira's changelog.
This creates three critical gaps:
Automation triggers don't fire — Neither "Field value changed" nor "Issue updated" triggers detect JPD field changes (e.g., a user/people field like "Country Manager" being updated).
JQL CHANGED operator doesn't work — Since JPD field changes aren't in Jira's changelog, queries like "Country Manager" CHANGED AFTER -7d return no results, even though the change is clearly recorded in JPD's History tab.
No standard Jira field workaround — You cannot add standard Jira custom fields (e.g., User Picker) to JPD projects, so there's no way to work around this by using a field type that does write to the changelog.
What I'd like:
JPD field changes should write to Jira's changelog so that JQL's CHANGED, WAS, and CHANGED BY operators work for JPD fields.
JPD field changes should emit standard Jira issue events so that automation triggers ("Field value changed", "Issue updated") fire correctly.
Use case:
We use a JPD user field to assign ownership of ideas. We need to automate notifications and workflows when this field changes — something that works seamlessly for standard Jira fields but is completely broken for JPD fields, despite JPD already tracking the change history internally.
