hi! I am so happy to see that there is a "due date" category that I can use to customize my view in bugzilla. I don't see that section within the bug for me to configure, I'd love to add that in to help with bug management, please. I'm mainly operating within the Marketing (design / copy / video) components for Brand Engagement... but if this can be added to all of Marketing, that would be great. whichever is easier / faster. Please let me know if I can help clarify anything. and huge thanks in advance.
apologies, changing the title to reflect the right language: * Marketing "product" * Design/Copy/Video "Component"
As this requires a code push, it will show up after this weeks update sometime after Wednesday. Committing to: bzr+ssh://email@example.com/bmo/4.2 modified extensions/BMO/lib/Data.pm Committed revision 8750. dkl
wohoo! thank you :)
this change has been pushed to production.
Hi! just saw this added and am super excited. Thanks again. I have a question though wrt formatting. It seems to also include a time stamp? is it possible to change that? the time stamp isn't relevant to us and it adds extra noise that I'd rather avoid if I can. attaching a screenshot to show this. Let me know, thanks again.
(In reply to Tara (musingt) from comment #5) > Hi! just saw this added and am super excited. Thanks again. I have a > question though wrt formatting. It seems to also include a time stamp? is > it possible to change that? the time stamp isn't relevant to us and it adds > extra noise that I'd rather avoid if I can. attaching a screenshot to show > this. Let me know, thanks again. Unfortunately the Due Date custom field is of type DATETIME which contains a timestamp as well. To properly fix this we should backport bug 801664 to bmo/4.2 from upstream and then change the Due Date field to the new DATE type without timestamp. Of course this is only if people have not been inputting timestamps into the current field which may make it difficult to just switch over. Anyway, I am opening a new bug report about the porting and we can discuss this further there. bug 866248 dkl