Resolving quirky issue with stories assigned to projects and we can't reassign to a new project when initial project closes or we need to reassign. Has anyone else encountered this?

[Wesley8]

A few months ago, we discovered an issue with trying to reassign stories to new projects when a project completes.  When we try to reassign the active story to a new project, because SN assigns the story to the demand of the project that it is first assigned to, the only option that is presented is the old project that we are trying to close.  I guess if the project wasn't created from a demand, you don't have this issue (I haven't tested that).

SN recommendation is to copy the story to a new story and assign it to the new project.  That is an issue for us as : 1) We lose the link to the Enhancement record linked to the story (yea, we use enhancements, long story) 2) We lose the work note history from the story.

We set up some testing in our Test environment and verified that we can programmatically reset the Demand field and then reassign the story to the correct project.  We did not find any unintended consequences on the Story or the Demand record.

We are also reviewing if we can create a button, accessible based on role, to clear the demand for a story record to allow for correcting in the future.

We currently have 57 stores in our PROD environment that need to be updated and included in different projects.

As I shared, we have reached out to SN, but they said is working as designed; however, for us, that design does not match our workflow.  

Has anyone encountered this same issue?  

Thanks, Wesley

[Namita Mishra]

Hi @Wesley,

The workflow is not clear to me.

Are you assigning the stories to the demand and then creating the project from that demand?

If you can share the workflow and also at each step what is being done & why (objective) and also what is expected; that would help in gaining a better understanding...

Thanks,

Namita Mishra

[Wesley8]

The workflow is as follows:

1. Demand is created and approved for a release.
2. A project is created from the approved Demand.
3. The project is created as a hybrid project with multiple team agile phases.
4. Stories are created and assigned to project and hybrid phases.  At this point, SN assigns the project's demand to the story's demand field.
5. The project ends, but stories are not completed and need to be assigned to a new release.
6. New demand is created and approved for a new release.
7. New Project created from the Demand
8. New Project is created as a hybrid project with multiple team agile phases.
9. Stories on the previous project that need to be assigned to the new release can't be assigned to the new release project because SN had populated the previous project's demand in the stories demand field.
10. At this point, we have to go in and programmatically clear the demand from the stories you want to assign to the new project.  

SN indicates the solution is to copy these stories and then assign them to the new project.  Our issue is twofold 1) We lose work notes from the story. 2) Our stories are created from approved Enhancements, not Epics, so when you copy the story, you lose the connection to the Enhancement. 

Please let me know if there are still questions.

Thanks.

[brody nienow]

I think the workflow has some issues here. Maybe, the stories from the demand of the project are the ultimate goal.

[Wesley8]

Brody, see my response to Namita for workflow.  Thanks