Dhruti Patel
- Login: DPatel
- Organization: AQM Technologies
- Registered on: 2025-07-07
- Last connection: 2025-07-16
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 0 | 0 | 0 |
Reported issues | 1 | 1 | 2 |
Activity
2025-07-10
-
08:35 Redmine Defect #42995 (New): Custom field created under Activities (time tracking) is not listed in the list of fields (Administration- Settings - Time Tracking)
- I have created a grouping of activities *Category - Activity* defined under Enumerations - Activities (Time Tracking)...
2025-07-09
-
09:50 Redmine Defect #42967: Fields marked as Read-only in a Tracker against a status , disappears from the screen instead of disabling the edit to the filed
- Able to get the resolution.
All fields would be visible to the user as read only in the displayed issue, however whe... -
07:04 Redmine Defect #42967: Fields marked as Read-only in a Tracker against a status , disappears from the screen instead of disabling the edit to the filed
- Thanks for the update.
Request if you can share some examples of how to define trackers to indicate segregation be...
2025-07-07
-
08:56 Redmine Defect #42967: Fields marked as Read-only in a Tracker against a status , disappears from the screen instead of disabling the edit to the filed
- Environment Details
nvironment:
Redmine version 6.0.5.stable
Ruby version 3.3... -
08:42 Redmine Defect #42967: Fields marked as Read-only in a Tracker against a status , disappears from the screen instead of disabling the edit to the filed
- Basis the review of an earlier defect Defect #41247 response provided to user
Redmine applies the most-open rules ... -
08:21 Redmine Defect #42967 (Closed): Fields marked as Read-only in a Tracker against a status , disappears from the screen instead of disabling the edit to the filed
- I have created an issue tracker where I want to disable the field updated during issue creation to be disabled but sh...
Also available in: Atom