Hi @stchar, Thank you for the PR.

I can agree that the default behavior for label edit should be to append the labels so that we won't accidentally lose the data. But, Instead of introducing a new flag label-append, I would go with changing the current behavior of the flag label to append the labels instead of overriding them (better than accidentally overriding the data IMO).

Also, let's keep table view as is. We can do a wide variety of things with Jira, and it may not be possible to incorporate everything, and I would like to keep things as simple as possible. A better thing to do would be to make the tool extensible so that devs can add new features on top of the existing one (using plugins).

Hi @ankitpokhrel, thanks for the input. I've removed the labels field form the issue view.

Regarding label-append I have a concern that if I change default behavior of -l flag which is now rewrites the label filed. I'll break the backward compatibility.

And people who already use it a lot they may be frustrated. Because they are already ok that it rewrites the field and may have some scripts on top of it. So now its not an architecture miss rather than a feature )) That's why I added additional flag to change the behaviour. What do you think?

@stchar that's a valid concern, but we are still in v0, and as per semantic versioning, that's acceptable. Be assured that we won't have any breaking change once we reach v1.

From the doc

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

@ankitpokhrel, ok cool, will rework it.

@ankitpokhrel, it's done.

@ankitpokhrel, cannot see your comments. Did you submit the review?