-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default template not applied automatically #35
Comments
Thank you for contributing to Redmine Issue Templates plugin!' first issue |
We face a similar problem. |
Does using code from the 0.3-stable branch cause the same problem? |
Well I tried to switch to the 0.3-stable branch and it doesn't seem to work at all : the issue template is not applied, and the "issue template" field is not present in the new issue page, even if I set the template as default for the default tracker. |
We do have the same problem on latest |
Any update on this issue? I have faced the same issue, unable to resolve. |
A small update on this issue, it looks like a race condition. I reproduced the bug several times, and I noticed that :
|
Fix in Pullrequest works for reload after change tracker! #63 |
Summary
When creating an issue on a tracker other than the default tracker for a project, the template is not applied automatically.
Description
When creating an issue, you can select the tracker in the project.
Let's say you have a project with 3 trackers : tracker1, tracker2, tracker3.
Tracker1 is the default tracker for this project.
If you apply an issue template as default template for tracker1 : when you create an issue, the template is applied.
If you apply no issue template for tracker1, but apply an issue template as default template for tracker2 : when you create an issue, at first the template is not applied, which is OK, because tracker1 is selected by default. Then, when you change the tracker to tracker2, I would expect the default template to be applied, but it is not (altough it is shown and can be selected by the user).
Environment
I tried it with all other plugins disabled, the behaviour is the same.
Visual Proof / Screenshot
The text was updated successfully, but these errors were encountered: