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

kanban board notes #12513

Open
luwol03 opened this issue Aug 17, 2020 · 4 comments · May be fixed by #29045
Open

kanban board notes #12513

luwol03 opened this issue Aug 17, 2020 · 4 comments · May be fixed by #29045
Labels
proposal/accepted We have reviewed the proposal and agree that it should be implemented like that/at all. topic/projects type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@luwol03
Copy link

luwol03 commented Aug 17, 2020

Allow notes in an project board which are not related to an issue, like github have it.
IMG_20200817_235150

IMG_20200817_234916

@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Aug 18, 2020
@Extarys
Copy link

Extarys commented Sep 4, 2020

Yes, like custom tasks.
Not sure if the new Kanban implementation have end date, but custom tasks should have the same level of options as issues in the kanban. (Ability to assign a person, a priority, tags, maybe a "private" options only team member would see)

@kcbimonte
Copy link

kcbimonte commented Nov 11, 2020

I say let's start small with just a comment and then add more functionality to the comment as time goes on. I'm proposing the following table definition for a comment:

Create Table Project_Comment (
  ID bigint primary key,
  Project_ID bigint not null,
  Project_Board_ID bigint not null,
  Comment Text not null,
  creator_id bigint not null,
  created_unix bigint not null,
  updated_unix bigint not null,
  Foreign Key (Project_ID) references Project(ID),
  Foreign Key (Project_Board_ID) references Project_Board(ID)
)

That is mostly SQL, which might contain a syntax error somewhere. Also would like to propose the following flow:

  1. Create a Project Board
  2. On any card, click a plus icon to create a comment
  3. Fill out comment and click save
    • Alternatively, click Cancel to delete the comment.
  4. Move comment (if needed) to any card
  5. Promote comment to issue
    • Remove from comment table and add to issue table.
    • Everything for an issue can be obtained from the foreign key relationships

Definitely open to comments on this, but I think this is a very fair start.

@Wufus
Copy link

Wufus commented Aug 9, 2023

Still missing, but hope to be added

@denyskon denyskon added the proposal/accepted We have reviewed the proposal and agree that it should be implemented like that/at all. label Oct 9, 2023
@zokkis
Copy link
Contributor

zokkis commented Feb 1, 2024

any updates?

@zokkis zokkis linked a pull request Feb 4, 2024 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal/accepted We have reviewed the proposal and agree that it should be implemented like that/at all. topic/projects type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants