From 3caffd6572160eb79b440a53e6200eb98fa896a9 Mon Sep 17 00:00:00 2001 From: Stuart Olivera Date: Sun, 23 May 2021 15:27:49 -0700 Subject: [PATCH] Add API Token as alternative to account password Added additional instructions for enabling password-less JIRA accounts, which are necessary for managed Atlassian accounts which block traditional username/password authentication. --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 47c1294..aa81d85 100644 --- a/README.md +++ b/README.md @@ -47,8 +47,12 @@ The first time you run it, it looks like this: User name: (your JIRA user name. Note: If you use OAuth, you still have a user name mapping, - it's in your profile view) + it's in your profile view or is your email address) Password: + (your JIRA password. + Note: If you use a managed account that doesn't allow passwords, + navigate to Account Seetings > Security > Create and manage API + tokens. An API Token can be used in place of the password. Store config? (y/n) y Running JQL: assignee = currentUser() order by priority desc