starred/1Remote

Fork 0

mirror of https://github.com/1Remote/1Remote.git synced 2026-04-25 13:36:03 +03:00

[GH-ISSUE #184] Bulk adding and removing common tags #2078

New issue

Closed

opened 2026-03-01 17:17:28 +03:00 by kerem · 6 comments

kerem commented

2026-03-01 17:17:28 +03:00

Owner

Originally created by @majkinetor on GitHub (Jan 21, 2022).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/184

Originally assigned to: @VShawn on GitHub.

Is your feature request related to a problem? Please describe.

You can't easily tag list of connections. Currently we have bulk SET of tags, that means all existing tags will be replaced with new set. However, that is usually not what one wants in bulk tag edit - we want to add/remove specific tag(s) without affecting existing ones.

For example:

C1 #db #web #linux
C2 #personal
C3 #foo #bar
C4 #web #db #linux

Now I say -#linux (#173) and get in results 2 & 3. Now I want to remember this result by adding new tag to it, lets say #temp so when I bulk ADD that tag I get:

C2 #personal #temp
C3 #foo #bar #temp

Now I can repeat this process and add #temp to results of other searches or by setting it on individual connections.
End result is that I have #temp group of connections, I didn't kill any other groups (#personal #foo #bar) and can use this new tag to run bulk connection functionalities temporary (I can delete that tag later) or forever (leave it there) - for example bulk connect, export, username change etc.

Describe the solution you'd like

Add new bulk option in list view - Tags. It will open popup with fields such as those (screenshot from web service I make):

Set new tags here will replace all tags and we have that already but it could be useful to repeat it here.

Describe alternatives you've considered
You must go one by one on connections and add tags. This is not efficient with a lot of connections.

Originally created by @majkinetor on GitHub (Jan 21, 2022). Original GitHub issue: https://github.com/1Remote/1Remote/issues/184 Originally assigned to: @VShawn on GitHub. **Is your feature request related to a problem? Please describe.** You can't easily tag list of connections. Currently we have bulk SET of tags, that means all existing tags will be replaced with new set. However, that is usually not what one wants in bulk tag edit - we want to add/remove specific tag(s) without affecting existing ones. For example: 1. C1 #db #web #linux 2. C2 #personal 3. C3 #foo #bar 4. C4 #web #db #linux Now I say `-#linux` (#173) and get in results 2 & 3. Now I want to remember this result by adding new tag to it, lets say `#temp` so when I bulk ADD that tag I get: 1. C2 #personal #temp 2. C3 #foo #bar #temp Now I can repeat this process and add `#temp` to results of other searches or by setting it on individual connections. End result is that I have `#temp` group of connections, I didn't kill any other groups (#personal #foo #bar) and can use this new tag to run bulk connection functionalities temporary (I can delete that tag later) or forever (leave it there) - for example bulk connect, export, username change etc. **Describe the solution you'd like** Add new bulk option in list view - Tags. It will open popup with fields such as those (screenshot from web service I make): ![image](https://user-images.githubusercontent.com/85767/150581039-c66e3319-5aa6-45c4-8338-19c25f4db4d0.png) Set new tags here will replace all tags and we have that already but it could be useful to repeat it here. **Describe alternatives you've considered** You must go one by one on connections and add tags. This is not efficient with a lot of connections.

kerem

2026-03-01 17:17:28 +03:00

closed this issue
added the
meta-enhancement

general-ux

general-supportive
labels

kerem commented

2026-03-01 17:17:29 +03:00

Author

Owner

@VShawn commented on GitHub (Jan 24, 2022):

Currently we have bulk SET of tags, that means all existing tags will be replaced with new set.

No, add new tag won't replace the existing tags. And IMO your UI screenshot is too complicated

1

2

3

4

@VShawn commented on GitHub (Jan 24, 2022): > Currently we have bulk SET of tags, that means all existing tags will be replaced with new set. No, add new tag won't replace the existing tags. And IMO your UI screenshot is too complicated # 1 ![image](https://user-images.githubusercontent.com/10143738/150738460-971831a8-2d09-4585-be91-a2cc1eca48f8.png) # 2 ![image](https://user-images.githubusercontent.com/10143738/150738687-31af41ec-a8bc-4a86-9fc6-26fef13a484a.png) # 3 ![image](https://user-images.githubusercontent.com/10143738/150739901-0062d24d-5c0a-4e59-ba59-7c548b59eb5e.png) # 4 ![image](https://user-images.githubusercontent.com/10143738/150739936-b39760df-5ab4-4922-81ad-a513637bfbf5.png)

kerem commented

2026-03-01 17:17:29 +03:00

Author

Owner

@majkinetor commented on GitHub (Jan 24, 2022):

Ah, it already works, how did I miss this....

Removing common tag isn't possible tho that easily but thats minor point.

@majkinetor commented on GitHub (Jan 24, 2022): Ah, it already works, how did I miss this.... Removing common tag isn't possible tho that easily but thats minor point.

kerem commented

2026-03-01 17:17:29 +03:00

Author

Owner

@majkinetor commented on GitHub (Jan 24, 2022):

Maybe you could update Tag diffing actually:

If I have 3 connections all having different tags, but all share few of them, then you could present it that way:

1. #1 #2 #3
2. #a #b #c #3 #1
3. #1 #3 #d #f

So when I bulk edit this I have <different options> while here it could be <different options> #1 #3.

With this, you could remove #1 and #3 on all.

@majkinetor commented on GitHub (Jan 24, 2022): Maybe you could update Tag diffing actually: If I have 3 connections all having different tags, but all share few of them, then you could present it that way: ``` 1. #1 #2 #3 2. #a #b #c #3 #1 3. #1 #3 #d #f ``` So when I bulk edit this I have `<different options>` while here it could be `<different options> #1 #3`. With this, you could remove `#1` and `#3` on all.

kerem commented

2026-03-01 17:17:29 +03:00

Author

Owner

@VShawn commented on GitHub (Jan 25, 2022):

ahh So when I bulk edit this I have <different options> while here it could be <different options> #1 #3.

I have already planned to do this, but I don't know why I missed it...

@VShawn commented on GitHub (Jan 25, 2022): ahh `So when I bulk edit this I have <different options> while here it could be <different options> #1 #3.` I have already planned to do this, but I don't know why I missed it...

kerem commented

2026-03-01 17:17:29 +03:00

Author

Owner

@majkinetor commented on GitHub (Jan 25, 2022):

OK, I will reopen this then .

@majkinetor commented on GitHub (Jan 25, 2022): OK, I will reopen this then .

kerem commented

2026-03-01 17:17:29 +03:00

Author

Owner

@VShawn commented on GitHub (Jan 26, 2022):

this ticket has been done yesterday by github.com/VShawn/PRemoteM@df4e637ee1

noticed CI is dead

@VShawn commented on GitHub (Jan 26, 2022): this ticket has been done yesterday by https://github.com/VShawn/PRemoteM/commit/df4e637ee1325870cca64d791696e35df47eb12e noticed CI is dead

No milestone

No project

No assignees

1 participant

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

starred/1Remote#2078

No description provided.

Rows
Columns