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

[HDX-253] Persist Custom Columns #152

Open
MikeShi42 opened this issue Dec 12, 2023 · 5 comments · May be fixed by #406
Open

[HDX-253] Persist Custom Columns #152

MikeShi42 opened this issue Dec 12, 2023 · 5 comments · May be fixed by #406
Assignees
Labels
Medium priority Created by Linear-GitHub Sync
Milestone

Comments

@MikeShi42
Copy link
Contributor

When a user adds a custom column to a search and saves the search, we should also persist the custom columns they've added as well. This would involve adding the custom column as a property to the saved search in the DB.

Related to: #27

From SyncLinear.com | HDX-253

@MikeShi42 MikeShi42 added the Medium priority Created by Linear-GitHub Sync label Dec 12, 2023
@ptdatta
Copy link

ptdatta commented Feb 3, 2024

Hey @MikeShi42 Can I give it a try?

@Seikilos
Copy link

I noticed that this issue is getting more important. When I am using high performance logging in C#, I naturally have to fall back to structured logging format. Visually getting a hint on what is going on has now become very tedious, because now I only see something like:

  • Data {Data} has {Result}
  • Data {Data} has {Result}
  • Data {Data} has {Result}
  • Data {Data} has {Result}
  • Data {Data} has {Result}
  • Data {Data} has {Result}
  • Data {Data} has {Result}

I now have to configure columns all the time between different saved queries as they have very different column names. Since they are nowhere persisted, it becomes hard to actually see, what is going on.

Copy link

ellipsis-dev bot commented Feb 27, 2024

Sorry, Ellipsis encountered a problem while generating a pull request. Our team has been alerted and is investigating. (wflow_HOffSZs20EL18Low) 🤖

@JeyRathnam
Copy link
Contributor

@MikeShi42 Can I work on this?

@MikeShi42
Copy link
Contributor Author

@ptdatta - ah sorry totally missed your comment 🙁 If there's anything else you find interesting to contribute to please don't hesitate to ping or feel free to ping us on Discord as well if any of your comments are getting lost in our GH notifications.

@JeyRathnam - I'll assign to you, let me know if you have any issues (or feel free to ping me on Discord) 😄

@JeyRathnam JeyRathnam linked a pull request May 23, 2024 that will close this issue
@MikeShi42 MikeShi42 modified the milestones: v.35, v.36 May 23, 2024
@MikeShi42 MikeShi42 modified the milestones: v.36, v.37 Jun 3, 2024
@MikeShi42 MikeShi42 modified the milestones: v.37, v.38, v.39 Jun 10, 2024
@MikeShi42 MikeShi42 modified the milestones: v.39, v.40, v.41 Jun 24, 2024
@MikeShi42 MikeShi42 modified the milestones: v.41, v.42, v.43 Jul 8, 2024
@MikeShi42 MikeShi42 modified the milestones: v.43, v.44 Jul 22, 2024
@MikeShi42 MikeShi42 added this to the v.45 milestone Jul 29, 2024
@MikeShi42 MikeShi42 modified the milestones: v.45, v.46 Aug 5, 2024
@MikeShi42 MikeShi42 modified the milestones: v.46, v.47, v.48 Aug 12, 2024
@MikeShi42 MikeShi42 modified the milestones: v.48, v.49 Aug 26, 2024
@MikeShi42 MikeShi42 modified the milestones: v.49, v.50, v.51 Sep 2, 2024
@MikeShi42 MikeShi42 modified the milestones: v.51, v.52 Sep 16, 2024
@MikeShi42 MikeShi42 modified the milestones: v.52, v.53, v.54 Sep 23, 2024
@MikeShi42 MikeShi42 modified the milestones: v.54, v.55 Oct 7, 2024
@MikeShi42 MikeShi42 modified the milestones: v.55, v.56 Oct 14, 2024
@MikeShi42 MikeShi42 modified the milestones: v.56, v.57 Oct 21, 2024
@MikeShi42 MikeShi42 modified the milestones: v.57, v.58 Oct 28, 2024
@MikeShi42 MikeShi42 modified the milestones: v.58, v.59 Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Medium priority Created by Linear-GitHub Sync
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants