task #43
closed
unable to set recurrence on 5.0.5
Description
Hi,
I freshly installed the plugins, follow all the required steps from installation, to service restart, configuration, rights tuning and module activation...
I'm still not able to set or modify a recurrence.
The cronjob succeed, but without any logs (out or err).
As I'm very keen to make this plugin works, how may I help you to find out the culprit ?
Regards,
Nono
Files
| issue_tab.png (9.85 KB) issue_tab.png | |||
| issue_new.png (36.8 KB) issue_new.png | |||
| issue_edit.png (26.5 KB) issue_edit.png |
Updated by cryptogopher over 1 year ago
- Tracker changed from task to 3
- Status changed from new to in progress
Hi,
What do you mean by "not able to set or modify a recurrence"? You can't see the "Recurrences" tab on issue page? Could you provide some screenshot depicting your problem?
Updated by Nono-m0le over 1 year ago
- File issue_new.png issue_new.png added
- File issue_tab.png issue_tab.png added
I can see the "Recurrences" tab, but it's always states "No data to display" => I guess this is normal on a new instance.
But When I created a new issue, I don't have any option to add a reccurences :
Updated by
Updated by cryptogopher over 1 year ago
You need to save your issue first.
Then after you open it, there will be "Recurrences" area right below issue "Description" - if you have set permissions correctly.
"Issue recurrences" tab is there to just show you all configured recurrence schemes. You cannot add recurrence from there.
Updated by Nono-m0le over 1 year ago
- File issue_edit.png issue_edit.png added
I don't have anything when I edit an existing issue.
Does it HAVE to be a new issue (meaning, SINCE I installed the plugin) ?
Updated by Nono-m0le over 1 year ago
I actually just find it ...
I was expecting something when I CREATE the issue, somehow I didn't completly understand the screenshot on github, my bad ...
Thanks !
Updated by cryptogopher over 1 year ago
- Status changed from in progress to closed
The approach of editing Recurrences only after issue has been created was taken to follow Redmine's similar logic of adding Related issues etc.
Thanks to that issue creation form stays relatively compact.