-
Notifications
You must be signed in to change notification settings - Fork 6
Log the Jira issue key #22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
MattMofDoom
wants to merge
36
commits into
aliozgur:master
Choose a base branch
from
MattMofDoom:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
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
…d due date as static or dynamic properties
…time) and due date as static or dynamic properties" This reverts commit 7367f16.
…d due date as static or dynamic properties
Append "Consider installing Seq.App.EventSchedule app so that you can feed this property automatically from the event log stream." to estimate related properties' help text
Pull from master
…lebars.dll and seqapps.commons.dll during Nuget package build
Hi @aliozgur Just giving this a nudge. The Jira app works fantastically now but definitely could use this ability to log the Jira issue key and URL after the issue is created. Cheers, Matt |
@aliozgur I've pushed a dependency update. However "Here be dragons" - I have not tested that there are no breakages with Seq. Recommend a test rig. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi @aliozgur ,
Hope you're well. After running for some time on the current version, I've added a small enhancement that logs the Jira issue key and URL once the issue is created.
This just helps with traceability and reconciliation between Seq and Jira 😊
Cheers!
Matt