Skip to content
This repository has been archived by the owner on Jun 8, 2023. It is now read-only.

added priority field to issue description #1385

Merged
merged 1 commit into from Apr 1, 2014

Conversation

Restuta
Copy link
Contributor

@Restuta Restuta commented Mar 26, 2014

If JIRA issue has a priority it will be displayed with other issue fields, since it's one of the most useful properties

If JIRA issue has a priority it will be displayed with other issue fields, since it's one of the most useful properties
@Restuta Restuta changed the title added priority field to ticket description added priority field to issue description Mar 26, 2014
@technicalpickles
Copy link
Contributor

This looks fine to merge. I'd just like to mention I'm looking for someone to take over this and other JIRA scripts if you are looking to contribute more 💖 Here are the open issues: https://github.com/github/hubot-scripts/issues?labels=jira&state=open

cc #1113

technicalpickles added a commit that referenced this pull request Apr 1, 2014
added priority field to issue description
@technicalpickles technicalpickles merged commit 96f64df into github:master Apr 1, 2014
@Restuta
Copy link
Contributor Author

Restuta commented Apr 1, 2014

Thank, and what are the version policy for package.json? Since to get scripts updated automatically version has to change, so should I increase version with every pull request?

@technicalpickles
Copy link
Contributor

There's manual commands to run (ie npm publish), so I prefer not having the package.json updated in PRs. That way, I can bump the file, and git tag the release, and then npm publish, so we know there's a consistent sha between what's tagged and what's npm published.

I'll do a publish in the next day or so.

This is actually one reason I'd prefer more external packages, so they can be on completely different release lifecycles.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants