Is it normal behavior for the Job details page to update the state of "pickup" before assigning an asset?

[ahmdfsl]

No description provided.

[thehoneymad]

Very good question indeed. And I think this is TaskCat's fault. Im not sure though. But in any case, if you think this is a backend bug, I'd expect a ticket in TaskCat.

@faisalgobd nice work!

[ahmdfsl]

@thehoneymad Thanks. I'm not really sure if it needs to come from TaskCat.
We also need to stop user from assigning new asset once the "delivery" state is at "completed" status.
@tareq89 can we manage it from frontend?

[thehoneymad]

@faisalgobd yes its possible but the backend is always supposed to know what should and should not be done. So, these should be logged in TaskCat too

[ahmdfsl]

@thehoneymad I've created ticket at TaskCat. #90

[tareq89]

Yes

-----Original Message-----
From: "faisalgobd" [email protected]
Sent: ‎8/‎4/‎2016 3:53 PM
To: "NerdCats/T-Rex" [email protected]
Cc: "Muhammed Tareq Aziz" [email protected]; "Mention" [email protected]
Subject: Re: [NerdCats/T-Rex] Is it normal behavior for the Job details pageto update the state of "pickup" before assigning an asset? (#63)

@thehoneymad Thanks. I'm not really sure if it needs to come from TaskCat.
We also need to stop user from assigning new asset once the "delivery" state is at "completed" status.
@tareq89 can we manage it from frontend?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.