Hi Tracy - I think Teale is offering good advice. Hiding options is clean and maintains reporting integrity. Try testing it in SB01

Hi Jeremy, I like the concept of having an option to “enable”. This would allow the Admin to maintain some controls over Governance, e.g. “if you don’t remember to delete the content in the critical custom field, we will no longer allow you to have the privilege to copy a project”. This ability ...

Hi @jeremy. I am not sure that finding fields for "deleting" is the issue. It's more about determining the impact a field change could have. We had to do this for a client. Use Case was about finding what reports were impacted by making the field "change" so that the report could be edited - (e.g...

hi @Jeremy Flores‚ This topic came up with a client just last week. The client has PM's who use the copy feature often because it is the quickest way for them to recreate a similar project. But when they do this, it is causing issues with an integration and a custom field that PM's neglect to clea...

I love the functionality to be able to call out certain text by using Bold, Italics and Underline features that exist in the new Rich Text Fields. This makes is so much easier to create a space that leads the eye around the page and allows users to focus on what's important. But what about Bullets...

there are a lot of related ideas around Scrum and Kanban. I wonder if WF has considered corralling them all and creating one initiative to improve the functionality in WF overall?

Hi Elissa - I would like to be included in a discussion as well. I think there are a number of different use cases. However, in general terms, the concept of creating an other layer for bucketing objects is ideal.