Bug - # times worn incorrectly calculated
Gemma Minihan
- I wore a new pair of boots twice in one day, in 2 different outfits.
- #timesworn is showing as ‘once’
- this means cost per wear (cpw) is incorrect.
Screenshots attached
Please could you check the logic for #timesworn is per scheduled (date in the past) outfit, not per day as I suspect it is? Please can you make sure any fix is retroactive - cpw is one of the most important metrics! Thank you :)
Ludwig Henne
Hi Gemma,
currently the CPW is indeed calculated as in one day = one wear. It is not a bug but on purpose for now. The reasoning is that often you might switch parts of your outfit but not consider it a 2nd wear.
Example: I put on a watch in the morning that I keep on the entire day but I swap my jacket or shoes for a 2nd outfit for dinner. Your proposed solution would track that watch as 2 wears even though I only wore it once as in I never took it off that day.
I would argue if you wear the same shoes for 2 occasions/outfits on one day, it's still considered one wear.
But I am curious to hear more opinions from the community on this 🙂 - obviously if the majority of people wants to track things differently I'm open to making changes.
Gemma Minihan
Ludwig Henne working as expected :D
Fair enough, I will follow feedback as interested if I am an outlier here!
C
C. P.
Ludwig Henne hello, for me, one day is also one wear. If I wear an outfit at home, then just change my cardigan and add shoes to go out, I still consider that I wore my other items (pants, shirt, socks, etc.) only once.
If I wear three outfits in one day, one for work, one for groceries shopping, and one to visit friends, but some items are the same (e.g. shoes), I wouldn’t want them to count as three wears, it would wrongly lower the cost per use.