alfred-jira
alfred-jira copied to clipboard
Create an issue
Add the ability to create a new issue for a project from the workflow.
This would be my number one feature request! 👍
Is there anything I can do to help with this issue? The ability to brain dump issues quickly would be wonderful. Thanks for all your work- the workflow is amazing (a web app to change settings? seamless download of icons?! wow)
@andrewgiessel, thanks for the kind words. I'm glad you're finding the workflow useful. Unfortunately, I've been a little swamped at work lately and haven't been able to focus on coming up with a good implementation of this feature. If you have something in mind, definitely submit a pull request!
Where would I start in the codebase? Is there a JIRA API page? Is there an example command to base this on? On Thu, Oct 5, 2017 at 12:28 Stephen Pennell [email protected] wrote:
@andrewgiessel https://github.com/andrewgiessel, thanks for the kind words. I'm glad you're finding the workflow useful. Unfortunately, I've been a little swamped at work lately and haven't been able to focus on coming up with a good implementation of this feature. If you have something in mind, definitely submit a pull request!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/steyep/alfred-jira/issues/1#issuecomment-334519442, or mute the thread https://github.com/notifications/unsubscribe-auth/ABG3JeYCt2O6lIzOKwCSn0asKlJUaRxaks5spQO8gaJpZM4J-E2U .
I've pushed this feature to the feature/1-create-issue branch if you're interested in checking it out/giving me your feedback. Make sure to checkout the updates to the README.md for more info. Demo below:

Just tried it. Had to make one change to get it to work
let assignee = (users.find(user => user.username == issueConfig.assignee) || { name: '' }).name;
Nice catch @justinffs! Could you PR your change into feature/1-create-issue?
@steyep I've pushed @justinffs feedback to a branch and opened a PR to feature/1-create-issue #100
Issue Type
One thing I just noticed on the new Jira cloud (I have not tested on old Jira) is that settings isn't pulling in the list of issue types

They do appear when creating the issue

Is there a way I can store this preference by hand?
Reporter
It looks like reporter is now required

@timbroder the issue type / reporter should be pulled from your settings file (~/.alfred-jira/.config). The simplest thing to do would be to make a backup of that file, logout of the workflow and then log back in. That will force a refresh of all that data.
What should the keys be for that?
This is all that's in the create section
"create_issue_defaults": {
"assignee": "admin",
"project": "WAVE"
}
Sorry, @timbroder, it's been a while since I looked at this codebase and I was incorrect about how that data is being generated. The data returned by jira ► create ► issuetype uses the project as context whereas the list of issue types generated by the Angular app does not pass a project parameter. The two methods make requests to different endpoints. The app uses the rest/api/2/issuetype endpoint. Do you get results back from ${ your jira url }/rest/api/2/issuetype? You could also try to switch the API version to 3.
The issue's reporter should be defined as the user who is logged into the workflow (the user key in the ~/.alfred-jira/config.json file). https://github.com/steyep/alfred-jira/blob/feature/1-create-issue/lib/jira/create.js#L65
is this working?
@steyep any plan to merge into master?
Hah yeah, I thought did. I guess I forgot 🤦♂
This does not work for me; when I select 'Create Issue', it just falls out of the Jira workflow and opens a Google Search for that.
