Add support for reason for project cancelation

[fnisen]

When a project is being canceled/closed, we'd like to add a disposition field to explain what happened. Possible options: 1) spam 2) demo/test 3) went with competitor 4) price/cost 5) not a good fit for community 6) declined by our choice 7) customer didn't make decision/never heard back 8) customer decided to do it themselves

[vikasrohit]

@parthshah we can store the cancellation reason at root level of the project json, right? or do you think it makes sense to store it in details field JSON?

[vikasrohit]

On the contrary to what I have said above, I have made changes in the front end, without altering the project service, to allow setting the reason of cancellation. For now I have stored the reason of status changes in details JSON, rationale being that essentially it is the detail of the status changes. Further, I have taken the liberty to support track multiple status changes as well. These all status changes would be stored as an array of objects with following schema:

{
  fromStatus: [previous status],
  toStatus: [status changed to],
  timestamp: [timestamp of change],
  reason: [reason of the change]
}

Despite the support being added, UI is right now only adding reason for cancellation of the project. All changes are in separate branch https://github.com/appirio-tech/connect-app/tree/feature/project-cancellation-reason

[fnisen]

Thanks @vikasrohit. @parthshah please weigh in b/c I think you were already making some API changes to be able to track status changes. Also, I think we've instrumented project service to focus on the API, so having this on the front end may mean we can't reliably pull in the data. Finally, the reason is applicable mostly for cancellation. If a project moves phases in other cases, there's usually only one reason.

[vikasrohit]

@fnisen I guess we should ask a reason for project deletion as well.

[fnisen]

@vikasrohit good idea, but I think it's not critical. Deletion is supposed to be for when you're experimenting with project creation, so we can assume for now the user was not serious about the project.

[parthshah]

@vikasrohit nice thought on using details field. Sorry I missed your earlier post. I'm running a challenge to add cancellation reason At the root level along side status. For status history tracking, you don't want to burden the client with tracking history. Besides we shouldn't trust the client to do it right. This is definitely a service concern and should be done server side. I'm not planning on exposing this data through the api either, it will only be used for our tracking. @fnisen let me know if status changes need to be displayed on FE

[parthshah]

I should have the changes in dev by Thursday eod.

[vikasrohit]

Okay. Thanks @parthshah That means I have just update my changes to update the change reason at root level instead of details json. Right?

[vikasrohit]

One more thing, the new field would be used to store reason of the cancellation of the project or reason for the last status change? I am asking this to ensure if we are going support the project deletion reason in future.

[fnisen]

@parthshah - we don't need history of status changes in the FE right now. I could see it coming in handy in the future, for example with an admin tool or timeline feature. But, I think no need to build it just in case, if it's easy enough to make the change later.
@vikasrohit - I'm pretty sure we won't need the reason per status change, but I guess you can include it for maximum flexibility. Probably better for Parth to weigh in on this one.

[parthshah]

Field is called 'cancelReason' but can be used for delete action as well

…

On Tue, Feb 28, 2017 at 10:59 PM vikasrohit ***@***.***> wrote: One more thing, the new field would be used to store reason of the cancellation of the project or reason for the last status change? I am asking this to ensure if we are going support the project deletion reason in future. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#44 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB5Ufj75l7BEsHfkrHyozvf0DlWLZKcOks5rhRdcgaJpZM4MDSnF> .

[vikasrohit]

Thanks @parthshah for the update. Is it deployed to dev?

[parthshah]

Not yet but hope to have it deployed today

…

On Wed, Mar 1, 2017 at 11:07 PM vikasrohit ***@***.***> wrote: Thanks @parthshah <https://github.com/parthshah> for the update. Is it deployed to dev? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#44 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB5UfljsHl7sfA_pcnWG-wgVGI-_NY0Eks5rhmq7gaJpZM4MDSnF> .