Vote #74965
完了Parent task search and datepicker not available after changing status
0%
説明
I played a bit with read only field for trackers and users throughout all my Redmine setup, but now I found out a problem.
When I try to create a new issue, only Tracker, Status and Parent Task fields are visible, and Parent Task has its Magnifier lens image in it, so if I type something it the field, it starts the contextual search.
!NewIssueOK.png!
But then, when I change the status and the page is redrawn as per specific tracker/issue, Parent Task loses its Magnifier and the capability of search with it; same thing for due date and start date datepicker, not available at all.
!NewIssueKO.png!
Finally, if I create the issue and then try to update it, both Parent Task search and datepicker are back as usual.
Any idea?
My Redmine installation comes from Bitnami stack 2.4.2-0, containing:
- Redmine 2.4.2
- Apache 2.4.7
- ImageMagick 6.7.5
- MySQL 5.5.34
- Subversion 1.8.4
- Git 1.8.3
- Ruby 1.9.3-p484
- Rails 3.2.16
- RubyGems 1.8.12
and plugins:
- extended fields 0.2.2
- projects table plugin 0.0.4
- DMSF 1.4.7 stable
- Redmine Multi Column Custom Fields plugin 0.0.1
- Redmine Tracker Control plugin 1.0.8
journals
This was due to the fact that the description field was read-only when the page is loaded.
It's fixed in r12941, thanks for poiting this out.
--------------------------------------------------------------------------------
Sorry JPL,
following your explanation I tried disabling read only attribute for Description field, in order to get the scripts back without having to wait for 2.4.4 release, but with no luck: I see also Description before changing status, but the datepicker and contextual search for Parent task are still missing. Even with all global fields without read only property (I left other custom fields as read only, but I don't think it could be related), the problem is present.
I didn't restart Redmine process after workflow modification, but I don't understand why this should be necessary... Are you sure your patch will work in any condtion?
Thank you for your great support.
--------------------------------------------------------------------------------
Well, I was able to reproduce with the configuration as in your first screenshot and r12941 fixed it. Tested with Chrome and Firefox.
Maybe a plugin issue, please try this out without any plugin.
--------------------------------------------------------------------------------
I'm closing it. Please open a new ticket if you find another case that breaks.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
related_issues
relates,Closed,16270,Patch not working as expected from #16161 in r12491