-
-
Notifications
You must be signed in to change notification settings - Fork 55
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
Add "Status Change Date" field to issue. #277
Conversation
new field seems ok, not breaking anything. column "Status Change Date" is perfect name IMHO. as for current functionality you mean "Last Action Date"? |
Hello. I couldn't see that feature in our system. So perhaps we don't even use it? What must definitely stay is "Submitted date", "Last updated date" and our custom field "Deadline" (which is actually rarely used). These are date selector fields that we use. |
@slay123 Those fields will stay for sure. Like I said, I don't think anyone really uses the old column, but in case they do I'm happy to rename the old field to "Status Action Date" |
e4c32c4
to
0614a16
Compare
Alright I've renamed that old field, a lot more places to change once I decided to be thorough :) Let me know if you see any problems |
phinx doesn't support php namespaces yet for migration classes
I've added a new field to the issue to track when the status was last changed and I've added it to the list issues page as well.
This name conflicts with some old, confusing functionality here (linked from the admin as "Customize Issue Listing Screen") which allows you to choose your own date field to display based on what the status is. I can see some value in this functionality, but I don't use it and am not sure if anyone else does either.
I would like to either rename it to "Status Action Date" (or something better, I'm open to suggestions) or remove the functionality.
Thoughts?