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

[GITLAB INTEGRATION] - add in Backlog bug #3933

Closed
pierrejo opened this issue Jan 24, 2025 · 4 comments
Closed

[GITLAB INTEGRATION] - add in Backlog bug #3933

pierrejo opened this issue Jan 24, 2025 · 4 comments

Comments

@pierrejo
Copy link

Your Environment

  • Version used: snap
  • Operating System and version: Ubuntu (24.04)
  • Desktop Environment: linux

Expected Behavior

When a task from a Gitlab issue arrives in a project by default, if the project has a backlog, then it arrives there and should stay there.

Current Behavior

When a task from an issue arrives in a project by default, if the project has a backlog, then it arrives in it, but after a while, it's automatically moved from the backlog into the project.

Even if I manually put the task back into the backlog without specifying that it's a “today”, it still comes back into the project after a certain amount of time (gitlab sync time?).

The other tasks I've created since Super-productivity, on the other hand, remain in the backlog.

Steps to Reproduce (for bugs)

  1. Add Gitlab Integration (from self-hosted instance with custom URL)
  2. Add an issue on Gitlab
  3. Check S-P and your project backlog
  4. The task will be moved up to the project

Console Output

There's no errors

@pierrejo pierrejo added the bug label Jan 24, 2025
Copy link

Thank you very much for opening up this issue! I am currently a bit overwhelmed by the many requests that arrive each week, so please forgive me, if I fail to respond personally. I am still very likely to at least skim read your request and I'll probably try to fix all (real) bugs if possible and I will likely review every single PR being made (please, give me a heads up if you intent to do so) and I will try to work on popular requests (please upvote via thumbs up on the original issue) whenever possible, but trying to respond to every single issue over the last years has been kind of draining and I need to adjust my approach for this project to remain fun for me and to make any progress with actually coding new stuff. Thanks for your understanding!

Copy link

Hello there pierrejo! 👋

Thank you and congratulations 🎉 for opening your very first issue in this project! 💖

In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. 👀

For more open ended discussions and/or specific questions, please visit the discussions page. 💖

@johannesjo
Copy link
Owner

I am unable to reproduce this. What kind of message appears, when the tasks are moved up? Can you maybe also copy the console output from when it happens here?

@johannesjo
Copy link
Owner

Nevermind! I was able to reproduce and fix this. Thank you very much!

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

No branches or pull requests

2 participants