I'm sure there is an easy way to do this but my brain is Kentucky Fried. (Plus I've got vacationitis.) I know I have to parse the JSON but unsure how to get all the lines from a custom field to parse. Ultimately, I'm trying to get the text from a field into an Issue's description.   Please tell me a...

Ideally, we want this OFF entirely for our instance, never to return, sent off to outer darkness where there is nothing but wailing and gnashing of teeth.   We want to share things with the higher-ups and we don't want this to get in the way of the reports we're developing for them.   I'm more than ...

And not only is it one we've never asked for...it's one that actively makes our jobs more difficult being evangelists for the platform.   And while we're at it, we also get the "We're working to make Adobe workfront better for you" survey. That needs to go too. WE want data to help our users, as we ...

  Seriously, can we please be rid of this thing? I've had complaints from users--one of whom from the LT here.    I complained about this in my prior life at Bristol Myers Squibb. At that time, I was told that this was integral. I don't know if this is true. All I know is that it annoys my users and...

Absolutely! The first taste was pretty great and useful. That said, there are many other pieces of data we could use within the Project Object. Even so, we really need this on the Issue Object as well. 

We *love* the new ability to customize project headers and looking forward to being able to mix in more fields. What we would *really love* is the ability to do this on the Issue level. We are heavy users of the Issue object and Fusion automations and being able to hide things (such as Status) would...