Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Typing convention for Backlog quick textbox

LongN February 22, 2018

Could we have "typing convention" in this quick text box to quickly create an issue like:

[Issue type] "issue summary" @userId /yyyy-MM-dd #Fix_version_name $sprint_name <other long description with markdown 2-spaces-linebreak here> 

Ex:

[Task] update feature xxx @@user1 /2018-02-23 #version1.6 $sprint5 <include 4 part:  1. xxx  2. yyy  3. zzz  4. ttt> 

 


then jira will create an issue with these information:

Issue Type:              Task
Issue Summary:      update feature xxx
Assignee:                user1
Due date:                2018-02-23 
Fix Version:             version1.6

Description: 

                               include 4 part:

                               1. xxx

                               2. yyy

                               3. zzz

                               4. ttt


and this issue will be added to sprint5

Above is all my need to quickly create an issue and add to my sprint, you are free to add more convention 

20180223_113233_Clipboard.png

 

1 answer

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 26, 2018

That quick create box can be used to help pre-define values for new issues created there.   However this is dependent upon the JQL filter being used for this board.   So you could go to the issue navigator in Jira and create a new JQL filter.  The details of this filter will be important, but I think you could create one like this:

project=abc and issuetype=task and assignee=user1 and fixversion=version1.6 and duedate=2018-03-03

By doing this, when you then assign this filter to a board, the new issues created at via this bottom quick create will have the values you defined there.  Meaning each issue will be in project ABC of issuetype Task, assigned to user1, with that fixversion, etc.

The thing about this, is that I'm not certain you can actually set a sprint value in this quick create.  The reason is this quick create is expected to place items into a backlog.  If you create an issue that already has a sprint value, it's not technically in a backlog.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events