-
Suggestion
-
Resolution: Duplicate
-
None
-
None
-
None
It would be great if there was an event fired when custom fields are added.
So much code that I have written is constantly checking the custom field configurations and field layouts despite the fact that these only change at most once every 24 hours or so.
It would be much cleaner if I could cache these queries that I making all the time of the custom field configuration.
What prevents me from doing it is that there isn't really a system wide notification of when custom fields or layouts change. I suppose I could hack DefaultCustomFieldManager, but I've grown tired and had my knuckles so bloodied by hacking into things, that instead I write this request.
Really I think what would be even more grand is if there were a long long list of events that were fired throughout Jira and then thing like caches would subscribe to them like when developing Java GUI's.
Right now almost all the Jira code base is very process driven.
- duplicates
-
JRASERVER-1984 Notification of project events
- Gathering Interest
[JRASERVER-23319] Fire events for things like adding a custom field, field configuration layout changes, etc.
Workflow | Original: JAC Suggestion Workflow [ 3056088 ] | New: JAC Suggestion Workflow 3 [ 3685215 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2608584 ] | New: JAC Suggestion Workflow [ 3056088 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2585649 ] | New: Confluence Workflow - Public Facing v4 [ 2608584 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2361796 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2585649 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2129419 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2361796 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2092552 ] | New: JIRA Bug Workflow w Kanban v6 [ 2129419 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 885680 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2092552 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 708290 ] | New: JIRA Bug Workflow w Kanban v6 [ 885680 ] |
Bugmaster Rank (Obsolete) | Original: 128830000000 | |
JIRA Support Rank (Obsolete) | Original: 146210000000 | |
Studio Rank (Obsolete) | Original: 130990000000 | |
Support Rank (Obsolete) | Original: 130990000000 | |
Workflow | Original: PM Feature Request Workflow [ 274330 ] | New: JIRA PM Feature Request Workflow v2 [ 708290 ] |
Issue Type | Original: New Feature [ 2 ] | New: Suggestion [ 10000 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
I would agree that this improvement request and JRA-1984 could both be part of a more generic 'expand the Jira event system' improvement.