I agree that this may be "logical" functionality in some cases, but it also proves to cause confusion when the task/issue is being assigned to another role.   In our case, our teams Scrum.  They unassign the user from the Scrum board but the role remains as the primary assignment.  When they try to ...

Agreed!  We have had some scenarios come up when using a typeahead field for tasks would be helpful.

This information would be helpful for a variety of reporting and auding purposes. +1

Description -We many times have a need to propose updates to project plans (tasks) that may impact the timeline.  However, the overall impact is not known until we update the dates on the tasks and the system calculates an overall project end date.  In some of these instances, we need to seek stakeh...

I know this is an old post but we have run into the same challenge.  Our best practice is to move the story to the next sprint, and create a copy that is put into the prior sprint for record keeping.  This keeps the all the history with the most current sprint.

Nevermind.  it only works if you assign them to a task or issue, or if you add then to the project ream (People tab).

This one might work: 

We are considering using business rules and would love to talk with anyone who has had success in implementing them.  What kind of business rules have you implemented?  What level of effort is needed to implement and maintain?   Any draw backs or lessons learned?

We are considering using Fusion in the near future.  Would anyone be willing to share their experience?  What kind of training did you need?  How fast did you dully adopt and get comfortable with it?  How much time do you spend in monitoring, maintaining, and updating Fusion?  Any draw backs, or les...

Have anyone has success in leveraging Scenario Planner to come up with Product Roadmaps?