Something went wrong while setting issue due date.
Possibility to know when was a lock put when we have a conflict
Closed
Possibility to know when was a lock put when we have a conflict
Hello, it would be nice to know when was the other lock put when there is a conflict.
It would help to guess if the conflict is genuine or not.
(from redmine: issue id 5157, created on 2016-09-21, closed on 2016-09-27)
- Relations:
- relates #4559 (closed)
- copied_to #5154 (closed)
- Changesets:
- Revision 64923acf by Côme Chilliet on 2016-09-22T13:12:21.000Z:
Fixes #5157 Using fdLockEntry for lock tokens and added timestamp to them
- Revision 0931fae7 by Côme Chilliet on 2016-09-22T13:13:05.000Z:
Fixes #5157 Using fdLockEntry for lock tokens and added timestamp to them
- Revision 624c7b99 by Côme Chilliet on 2016-09-26T12:58:46.000Z:
Fixes #5157 fdLockTimestamp was missing from ldap search
- Revision 3b836cfe by Côme Chilliet on 2016-09-26T13:03:52.000Z:
Fixes #5157 fdLockTimestamp was missing from ldap search
- Revision fd7bd429 by Côme Chilliet on 2016-09-26T14:10:49.000Z:
Fixes #5157 Fixed template code for date formatting
- Revision 9b1282a4 by Côme Chilliet on 2016-09-26T14:11:17.000Z:
Fixes #5157 Fixed template code for date formatting
- Custom Fields:
- Support contract: Silver