fix: resolve option parsing conflict in issue subcommands

[pchuri]

📋 Summary

Fixed a critical bug where filter options like --assignee, --project, --status were not being parsed correctly when using jira issue list subcommand. This was a follow-up fix to PR #13 - the buildJQL fix alone wasn't enough because the options weren't reaching the function due to Commander.js parent/subcommand option conflicts.

🎯 Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🧪 Test improvements
• 🔧 Code refactoring
• ⚡ Performance improvements

🔍 Changes Made

• Removed parent command's legacy options and action handler from bin/commands/issue.js
• Removed unused getIssueAction() helper function
• Updated tests in tests/commands/issue.test.js to verify subcommand structure
• All functionality now uses explicit subcommands (list, create, view, edit, delete)

🧪 Testing

• All existing tests pass
• New tests added for new functionality
• Manual testing completed
• Code coverage maintained/improved

📊 Test Results

Test Suites: 7 passed, 7 total
Tests:       91 passed, 91 total
Snapshots:   0 total
Time:        0.387 s

🚀 Deployment Notes

• No special deployment steps required
• Requires environment variable changes
• Requires dependency updates
• Other:

📝 Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

🔗 Related Issues

• Related to fix: handle currentUser assignee filter correctly in JQL #13

💬 Additional Notes

Root Cause:
Commander.js v11 has strict separation between parent command and subcommand options. When both parent and subcommand define the same options, the subcommand's options are ignored.

Before (Broken):

jira issue list --assignee=currentUser
# Options object: { "limit": "20" }  ❌ assignee missing

After (Fixed):

jira issue list --assignee=currentUser
# Options object: { "limit": "20", "assignee": "currentUser" }  ✓
# Generated JQL: assignee = currentUser()  ✓

This fix completes the work started in #13 by ensuring options are properly parsed and passed to the buildJQL function.

[Copilot]

Pull request overview

This PR fixes a critical bug where filter options (--assignee, --project, --status) were not being parsed correctly in the jira issue list subcommand due to Commander.js parent/subcommand option conflicts. The fix removes legacy parent command options and action handlers, ensuring all functionality uses explicit subcommands.

Key Changes:

• Removed parent command options and action handler that conflicted with subcommand options
• Deleted unused getIssueAction() helper function
• Updated tests to verify subcommand structure instead of parent command options

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

🎉 This PR is included in version 2.1.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀