Same process for us. We have the need for more than the default 4 issue types.

Thanks for the suggestion William. I took at quick look at this and my initial thought is that this isn't practical at a company level. It might be workable for one-off Slack Workspace / Workfront project integrations. However, at a company level all the setup and configuration for each project and...

Create a relationship connection between a Workfront project (or projects) to a single Slack Workspace Channel. My experience has been that a Slack workspace is created for a dev team that is focused on a single project or sometimes a small number of projects. With this connection in place the all...

Add a command to the Slack integration that would allow someone to post to the update tab of a project/task/issue from the Slack interface. an additional nice to have feature would be to be able to tag other users in that post.

Agile stories need to be a unique object type with their own set of attributes. They should not be treated like a waterfall task. The Story object should also have it own collection of sub objects. (Defects, Blockers, Tasks (Not waterfall WBS tasks), etc.)

Hear! Hear! The words Story Points and Hours should never be used in the same sentence. Except if confirming that the two have no relationship to each other. I also agree that effort on tasks in a story should NOT roll up and change the story points

I'd like to see this as a general change overall. When creating a custom field we should be able to have a 'name' and a 'display label'