gitnex/GitNex
41
855
Fork
You've already forked GitNex
47

Kanban Support #992

Open
opened 2021年10月07日 18:50:13 +02:00 by delight · 10 comments

# What do you want to address?

  • Bug
  • Feature
  • Suggestion

# Describe your matter briefly


It would be great to see at least rudimentary support for the kanban funtionality in GitNex as it is available in gitea/codeberg

What did you expect?


Rudimentary kanban support

Some additional details

  • The version of Gitea you are using: 1.15.3 (currently not supported by GitNex 4.0 -> already adressed in a another bug and planed for Milestone 4.1)
  • The version of GitNex you are using: 4.0
  • Source of installation (Play Store, F-Droid, APK): F-Droid
  • Current android version and phone model/manufacturer: Android 10
  • The type of certificate your instance is using (self-signed, signed): signed
  • How you used to log in (via password or token): password

We would appreciate some screenshots or stacktrace's, but this is also not required.



Thank you for your time.

## # What do you want to address? <!-- This step is required; examples are shown below --> - [ ] Bug - [X] Feature - [ ] Suggestion ## # Describe your matter briefly <!-- This step is required. --> <br>It would be great to see at least rudimentary support for the kanban funtionality in GitNex as it is available in gitea/codeberg<br> ##### What did you expect? <!-- Useful when addressing bugs --> --- <!-- This step is optional. --> <br>Rudimentary kanban support<br> ##### Some additional details <!-- Useful, when we are trying to reproduce a bug --> --- <!-- This step is optional; an example is shown below --> * The version of **Gitea** you are using: 1.15.3 (currently not supported by GitNex 4.0 -> already adressed in a another bug and planed for Milestone 4.1) * The version of **GitNex** you are using: 4.0 * Source of installation (Play Store, F-Droid, APK): F-Droid * Current android version and phone model/manufacturer: Android 10 * The type of certificate your instance is using (self-signed, signed): signed * How you used to log in (via password or token): password <br> ##### We would appreciate some screenshots or stacktrace's, but this is also not required. --- <!-- Screenshots and stacktrace's can go here. --> <br><br> - [x] I carefully read the [contribution guidelines](https://codeberg.org/GitNex/GitNex/src/branch/main/CONTRIBUTING.md). <br> #### Thank you for your time.
Member
Copy link
upstream https://github.com/go-gitea/gitea/issues/14299

As ForgeJo is now a hard fork, should we refer to/open upstream issues at ForgeJo rather that at Gitea? If so, forgejo/forgejo#5330 (comment) was recently opened.

As ForgeJo is now a hard fork, should we refer to/open upstream issues at ForgeJo rather that at Gitea? If so, https://codeberg.org/forgejo/forgejo/issues/5330#issue-876165 was recently opened.

I'm not sure about the current status of these projects or their affairs, but in my opinion, an issue should be opened on both repositories. Whichever one implements it will benefit the other as well.

I'm not sure about the current status of these projects or their affairs, but in my opinion, an issue should be opened on both repositories. Whichever one implements it will benefit the other as well.

+1 from me

With even some more context

https://vmst.io/@maikel/115700517053886061

+1 from me With even some more context https://vmst.io/@maikel/115700517053886061

@maikelthedev GitNex uses API for features addition. I still don't see any API available for kanban/projects (on Codeberg).

@maikelthedev GitNex uses API for features addition. I still don't see any API available for kanban/projects (on Codeberg).

I mentioned this issue there since they have already a feature request in open status with this

forgejo/forgejo#5330

I mentioned this issue there since they have already a feature request in open status with this https://codeberg.org/forgejo/forgejo/issues/5330

There's also this PR waiting to be tested to be merged but seems stuck since two months ago.

forgejo/forgejo#9384

There's also this PR waiting to be tested to be merged but seems stuck since two months ago. https://codeberg.org/forgejo/forgejo/pulls/9384

The seem to have merged what was necessary for this

The seem to have merged what was necessary for this

The seem to have merged what was necessary for this

What are you referring to? I can't see any merged PR related to this, and work is still happening on forgejo/forgejo#9384 and forgejo/forgejo#11304

> The seem to have merged what was necessary for this What are you referring to? I can't see any merged PR related to this, and work is still happening on https://codeberg.org/forgejo/forgejo/pulls/9384 and https://codeberg.org/forgejo/forgejo/pulls/11304

they are both closed @tobiasBora

they are both closed @tobiasBora
Sign in to join this conversation.
No Branch/Tag specified
main
release-14.0
android-17-permission-feature
release-13.0
release-12.0
release-11.0
release-10.0
release-9.0
release-8.0
release-7.0
release-6.0
release-5.5
release-5.4
release-5.3
release-5.2
release-5.1
release-5.0
release-4.5
release-4.4
release-4.3
release-4.2
release-4.1
release-4.0
release-3.5
release-3.4
release-3.3
release-3.2
release-3.1
release-3.0
release-2.5
release-2.4
release-2.3
release-2.2
release-2.1
release-2.0
release-1.5
release-1.1
release-1.2
release-1.3
release-1.4
14.0.0
13.0.1
13.0.0
13.0.0-rc4
13.0.0-rc3
13.0.0-rc2
13.0.0-rc1
12.0.0
11.0.0
10.0.1
10.0.0
9.0.0
8.0.3
8.0.2
8.0.1
8.0.0
7.0.0
6.0.0
5.5.0
5.4.0
5.3.0
5.2.1
5.2.0
5.1.1
5.1.0
5.0.1
5.0.0
4.5.0
4.4.0
4.3.0
4.2.2
4.2.1
4.2.0
4.1.0
4.0.0
3.5.1
3.5.0
3.4.0
3.3.0
3.3.0-rc3
3.3.0-rc2
3.3.0-rc1
3.2.0
3.2.0-rc1
3.1.2
3.1.1
3.1.0
3.1.0-rc2
3.1.0-rc1
3.0.1
3.0.0
3.0.0-rc3
3.0.0-rc2
3.0.0-rc1
2.5.1
2.5.0
2.5.0-rc4
2.4.1
2.4.0
2.3.2
2.3.1
2.3.0
2.2.2
2.2.1
2.2.0
2.1.3
2.1.2
2.1.1
2.1.0
2.0.0
1.5.0
1.1.0
1.2.0
1.3.0
1.4.0
Labels
Clear labels
Major-release
Minor-release
⚔️
Wontfix
This won't get fixed
⚙️
CI
Related to the CI/CD
⛏️
Breaking
Contains or will result in breaking changes
Fixed
Duplicate
Invalid
Question
❤️
Support
➡️
Frontport
➡️
Needs-frontport
🌐
Translation
🌠
Long-term
🎉
Feature
🎯
Enhancement
🏗️
Build
🐛
Bug
👋
Good-first-issue
💀
Deprecation
💡
Suggestion
💬
Discussion
💭
Brainstorming
💰
Sponsored
A feature which is sponsored by someone
💻
UI-UX
Related to the user interface or experience
📄
Documentation
📈
Performance
📌
Priority-critical
📌
Priority-high
📍
Priority-low
📍
Priority-medium
📡
Needs-feedback
📱
F-droid
📸
Release
🔒
Security
🔙
Backport
Bugfix ported to a release branch for point release
🔙
Has-backport
🔙
Needs-backport
🔙
Regression
🔭
Cannot-reproduce
🗄️
Repository
Related to this repository and it's management
🗒️
Changelog
🗓️
Summary
🤾
Google-play
🥑
Ready
🧪
Testing
🧺
Cleanup
🧺
Needs-cleanup
🧾
Confirmed
🩹
External-dependecy
🪒
Needs-refactor
🪒
Refactor
🪜
Upstream
🙇‍♂️
Help-wanted
🙇‍♂️
Needs-help
🚀
Improvement
🚨
Investigate
🛡️
Blocked
Waits for something else that must be solved first
🛰️
API-dependency
Requires and waits for changes in Gitea's API
🟦
Website
Related to the website
No labels
Major-release
Minor-release
⚔️
Wontfix
⚙️
CI
⛏️
Breaking
Fixed
Duplicate
Invalid
Question
❤️
Support
➡️
Frontport
➡️
Needs-frontport
🌐
Translation
🌠
Long-term
🎉
Feature
🎯
Enhancement
🏗️
Build
🐛
Bug
👋
Good-first-issue
💀
Deprecation
💡
Suggestion
💬
Discussion
💭
Brainstorming
💰
Sponsored
💻
UI-UX
📄
Documentation
📈
Performance
📌
Priority-critical
📌
Priority-high
📍
Priority-low
📍
Priority-medium
📡
Needs-feedback
📱
F-droid
📸
Release
🔒
Security
🔙
Backport
🔙
Has-backport
🔙
Needs-backport
🔙
Regression
🔭
Cannot-reproduce
🗄️
Repository
🗒️
Changelog
🗓️
Summary
🤾
Google-play
🥑
Ready
🧪
Testing
🧺
Cleanup
🧺
Needs-cleanup
🧾
Confirmed
🩹
External-dependecy
🪒
Needs-refactor
🪒
Refactor
🪜
Upstream
🙇‍♂️
Help-wanted
🙇‍♂️
Needs-help
🚀
Improvement
🚨
Investigate
🛡️
Blocked
🛰️
API-dependency
🟦
Website
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
6 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
gitnex/GitNex#992
Reference in a new issue
gitnex/GitNex
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?