186: fix: Jira integration improvements (config token, HTML error, status display)#187
Merged
186: fix: Jira integration improvements (config token, HTML error, status display)#187
Conversation
…s display (#186) 1. Support Jira token in config file: add token field to [tracker.jira], resolve priority: env vars > config file token. Config init now prompts. 2. Sanitize Jira HTML error responses: detect HTML bodies and replace with concise message instead of dumping entire HTML page on 401 errors. 3. Enrich `parsec status` with live tracker info: fetch ticket summary, tracker status, and assignee from Jira/GitHub Issues. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fix: Jira integration improvements (config token, HTML error, status display)
Ticket: 186
Shipped via
parsec ship 186