forward vision / guidelines for jira-cmd project
palashkulsh opened this issue · comments
@germanrcuriel thanks for adding me as a contributor, can you please share your vision for this project, and things I should keep in mind in general.
the things on top of my head are
- stable updates.
- more functionalities
Yeah, that's what I wanted. I had a refactor branch in my local machine but can wait. I share the same idea as you 😄 I will add you to npm package so you can publish updates too.
@germanrcuriel thats way too cool, in coming weeks , I'll be raising & merging PRs for new functionalities I've added in my fork . then will start working on adding new functionalities .
Nice!
@germanrcuriel, @palashkulsh : I'm putting this work to good use as well and would love to see it take on more life. Simply put, one of my top wishes would be to afford the user the ability to add or subtract labels to/from an issue.
@schamic thats a very good idea, I myself am writing the product details for more generic updating keys of issue after its created, will start vaguely in these phases
- just able to add any key/customfield
- ability to update key/customfield
since there are multiple customfields , will keep alias for these in config.json
Please share your thoughts as well.
@schamic I've added editing functionality in my fork of jira-cmd https://github.com/palashkulsh/jira-cmd
npm install -g https://github.com/palashkulsh/jira-cmd
interactive usage ==> jira edit MPP-731
non interactive usage ==> jira edit MPP-731 "labels::test1,test2"
Can you please use and comment, will be adding this in main repo after proper testing.
sure, let me know your findings.