You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've coded a new feature that I think would be a great addition to this plugin, but have one last piece that I need advice on.
DETAILS
We have a need at our company to be able to email digests based on custom criteria (e.g. custom fields). An easy way to accomplish this is using Redmines Issue Query. In the Redmine Digest Rule configuration, I added a new option in the Project dropdown "For any issue update on the selected issue query". Then a 2nd dropdown with a list of saved Redmine Issue Queries.
To persist the configuration, I saved the new project_selector issue_query and the Issue queries.id.
QUESTION:
Which approach would be preferable?
Option 1: Keep fields the same name
Since this is the easiest solution, I got this working, but I'm not sure it's the right solution.
SUMMARY:
I've coded a new feature that I think would be a great addition to this plugin, but have one last piece that I need advice on.
DETAILS
We have a need at our company to be able to email digests based on custom criteria (e.g. custom fields). An easy way to accomplish this is using Redmines Issue Query. In the Redmine Digest Rule configuration, I added a new option in the Project dropdown "For any issue update on the selected issue query". Then a 2nd dropdown with a list of saved Redmine Issue Queries.
To persist the configuration, I saved the new project_selector
issue_query
and the Issuequeries.id
.QUESTION:
Which approach would be preferable?
Option 1: Keep fields the same name
Since this is the easiest solution, I got this working, but I'm not sure it's the right solution.
Option 2: Add a new field issue_query_id
Option 3: Rename project_selector and project_ids fields
The text was updated successfully, but these errors were encountered: