Pavels AvensIt is a good ad-on, but there are some critical issues:
1. All datetime fields are being returned in Server time. There is no way to set Local time for datetime fields.
2. There is no possible to format custom fields (for example as Java SimpleDateFormat)
3. Notification does not work well with custom JQL functions. There is a bug in the add-on.
The add-on will not work on CRON event if a custom function uses JiraAuthenticationContext to get currently logged in user, which was passed to SearchService.
When running the add-on manually, there was a logged in user in current session. So there were no problems with custom functions. But when a custom function is being called by the add-on, JiraAuthenticationContext has no logged in user.
We have resolved it by passing a user from JQL custom function QueryCreationContext. But there will be a problem with other custom functions. Therefore setting the currently logged in user inside the add-on will be a good solution.
Was this review helpful?•
Vendor logoModus Create
Hi Pavels,
Thanks for reaching out. A few comments on your issues:
- 1. This is a good idea and something we could implement and we'll update the ticket NAS-54 once implemented.
- 2. The custom fields (like Date fields) are returned by the system date format so changing this format, will affect the output accordingly.
- 3. This one is already implemented in the product. You can select the user to “run as” in each configured notification.
If you have any other feature requests, just create or vote on tickets in our system.
Best Regards //Team Riada