Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ascents not correctly assigned to climbing session #4094

Open
killakalle opened this issue Jul 13, 2022 · 3 comments
Open

Ascents not correctly assigned to climbing session #4094

killakalle opened this issue Jul 13, 2022 · 3 comments
Labels
5: Enhancement Build up on existing function that adds or improve functionality significantly Area: Logbooks Ticking & tick lists

Comments

@killakalle
Copy link

To reproduce

  1. On Day 1 go climbing
  2. Log your ascents
  3. Sleep in the night
  4. On Day 2 remember that you forgot to log one of your climbs
  5. Log the ascent with ascent date of yesterday

Expected

  • Ascent is assigned to "session" of Day 1

Actual

  • Ascent is registered with a new "session" on Day 2

There are a couple of smaller issues that I've tried to capture in the following screenshot:

image

  • Maybe the problem just comes with the new term "session". It suggests that you have a climbing session. So, I expect that my ascent, which was in the same climbing session, is added to that very same session. However, on the theCrag website, the term "session" seems to refer to "stream event". And that in turn seems to be connected to the date of registration - and not necessarily the climbing session.
  • The ascent date, if it is in the past, is not shown consistently. When an ascent is only one day in the past, then the ascent date is not shown. You cannot distinguish those ascents from ascents of today - unless you open the ascent details. But that's maybe intended.
@rouletout rouletout added Area: Logbooks Ticking & tick lists 5: Enhancement Build up on existing function that adds or improve functionality significantly labels Jul 14, 2022
@Arzorth
Copy link

Arzorth commented Feb 10, 2023

+1

@Arzorth
Copy link

Arzorth commented Apr 24, 2023

I would like to request devs to consider this as a bug and not as an enhancement.

With the current behaviour, the session performance statistics don't bring useful information, because they point to the date the user logged the ascents, and not to the date the user climbed those ascents.

Regards,

José María

@Arzorth
Copy link

Arzorth commented Apr 24, 2023

check #4154 for more info

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5: Enhancement Build up on existing function that adds or improve functionality significantly Area: Logbooks Ticking & tick lists
Projects
None yet
Development

No branches or pull requests

3 participants