diff options
fix: Update lists with empty lines in between items
With a new dunbar update, unordered/ordered lists specify a possible
empty line between all list items (instead of being simple aliases for
bulleted/numbered list).
2 files changed, 13 insertions, 15 deletions
| -rw-r--r-- | src/tutorials/how-to-use-jira/cards.du | 20 | ||||
| -rw-r--r-- | src/tutorials/how-to-use-jira/projects.du | 8 |
diff --git a/src/tutorials/how-to-use-jira/cards.du b/src/tutorials/how-to-use-jira/cards.du index a73a152..68ca2d6 100644 --- a/src/tutorials/how-to-use-jira/cards.du +++ b/src/tutorials/how-to-use-jira/cards.du @@ -32,16 +32,15 @@ Each card has the following properties: [image ./img/fields-cards.png] -:bulleted +:unordered - =[Project]= - the [url ./projects.html project] this card is stored in - .p [image ./img/project-create-card.png] + [image ./img/project-create-card.png] - =[Issue type]= - the basic purpose of an issue (Improvement, Bug, ...) - .p [image ./img/issue-types.png] + [image ./img/issue-types.png] - :p :bulleted - [image ./img/story-type.png Story] - functionality or feature expressed as a goal, something like "As a user, I want to be able to pay for my order via PayPal" @@ -54,30 +53,29 @@ Each card has the following properties: - [image ./img/sub-task-type.png Sub-task] - an issue that is directly connected to another issue. This is used for when a given issue needs to be broken down into separate even smaller issues. - - =[Summary]= - a (required) brief explanation of the issue - .p [image ./img/summary-create-card.png] + [image ./img/summary-create-card.png] - =[Description]= - detailed explanation of the issue - .p [image ./img/description-create-card.png] + [image ./img/description-create-card.png] - =[Reporter]= - person who created the issue - .p [image ./img/reporter-create-card.png] + [image ./img/reporter-create-card.png] - =[Assignee]= - person who will work on the issue - .p [image ./img/assignee-create-card.png] + [image ./img/assignee-create-card.png] - =[Labels]= - tags with which you can organise even more the issue - .p [image ./img/label-create-card.png] + [image ./img/label-create-card.png] - =[Epic link]= - link of issue with type Epic - .p [image ./img/epic-link-create-card.png] + [image ./img/epic-link-create-card.png] ## Creating diff --git a/src/tutorials/how-to-use-jira/projects.du b/src/tutorials/how-to-use-jira/projects.du index 277e108..4ecccd2 100644 --- a/src/tutorials/how-to-use-jira/projects.du +++ b/src/tutorials/how-to-use-jira/projects.du @@ -101,18 +101,18 @@ Once you've made your choice, you will be met with three options: [image ./img/board-from.png] -:bulleted +:unordered - =[Board created with new Software project]= - creates a new project with a new board (has the name of the project). - .p [image ./img/npb.png] + [image ./img/npb.png] - =[Board from existing project]= - creates a board that gets the filter from another project - .p [image ./img/ntb.png] + [image ./img/ntb.png] - =[Board from an existing Saved Filter]= - as it says, you add to the project (indicated in the `[Location]` field) a board based on a saved filter - .p [image ./img/ntb-filter.png] + [image ./img/ntb-filter.png] ## Backlog |