Skip to content

'Assigned to you' issues should scope also in organisations #706

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.

Sign up for GitHub

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

Jump to bottom
Closed
1 of 3 tasks
rikvdh opened this issue Jan 20, 2017 · 2 comments
Closed
1 of 3 tasks

'Assigned to you' issues should scope also in organisations #706

rikvdh opened this issue Jan 20, 2017 · 2 comments
Labels
issue/duplicate The issue has already been reported.

Comments

@rikvdh
Copy link

rikvdh commented Jan 20, 2017 •
edited by tboerger
Loading

  • Gitea version (or commit ref): 1.0.0+116-g69b86378 (try.gitea.io @20-1-2017)
  • Git version: n/a
  • Operating system: n/a
  • Database (use [x]): n/a
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL) -- Login required
    • No
    • Not relevant
  • Log gist:

Description

If I look at the "Assigned to you" list of issues this only scopes in issues in my repositories. But I expect it to scope also the users organisation.

When I have an issue in my organisation assigned to me, the issue is not visible on the Assigned to me overview. When having multiple organisations this becomes fast very cluttered.
@lunny lunny added this to the 1.1.0 milestone Jan 20, 2017
@lunny lunny added type/bug type/enhancement An improvement of existing functionality labels Jan 20, 2017
@rikvdh
Copy link
Author

rikvdh commented Jan 29, 2017

See gogs/gogs#3560

@jeppech
Copy link

jeppech commented Jan 31, 2017

Duplicate of #503

@lunny lunny closed this as completed Jan 31, 2017
@lunny lunny added the issue/duplicate The issue has already been reported. label Jan 31, 2017
@tboerger tboerger removed type/bug type/enhancement An improvement of existing functionality labels Feb 10, 2017
@tboerger tboerger removed this from the 1.1.0 milestone Feb 10, 2017
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
issue/duplicate The issue has already been reported.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@lunny @tboerger @rikvdh @jeppech