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

stopping a logger refreshes the issue page and loses content #29

Open
nortonstreet opened this issue Jan 26, 2016 · 3 comments
Open

stopping a logger refreshes the issue page and loses content #29

nortonstreet opened this issue Jan 26, 2016 · 3 comments

Comments

@nortonstreet
Copy link

Love this plugin! Thank you for building it.

Unfortunately, I've run into a frustrating bug.

To reproduce:
1 Go to an issue.
2 Start a logger.
3 Hit Edit/Update for the issue.
4 Enter content in the Note field.
5 Stop the logger.

At this point I either have to lose my entered content or I can't stop the logger. Couldn't Stop simply put the time content on the page I'm already on? Or am I doing something wrong?

@speedy32129
Copy link
Owner

I'll look and see if we can add that as an enhancement. But the way it work is you would stop the time then enter your information or if I know I have a lot of documentation to write I'll enter 0 in the time and keep the time separate from the research or I'll hit the time and annotate the documentation time separately.

@nortonstreet
Copy link
Author

Thanks for looking into it! We try to encourage our folks to keep their notes in Redmine while they're working (we also use the Drafts plugin), so refreshing the page makes that workflow not possible. I'm happy to test or provide more feedback. Depending on the level of effort, my company may be interested in sponsoring development, too.

@speedy32129
Copy link
Owner

Sorry nortonstreet ... I took some time off. I'm back working on what is possible the last release of the free version. I'll see if I can figure out but on the core versions this issue doesn't come up but a warning does.
So seems to be fine so I'm guessing it may have something to do with the change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants