From 164cf2b137ce92860c39e94671ed220959a802e1 Mon Sep 17 00:00:00 2001 From: ireic Date: Tue, 7 Jan 2020 00:35:46 +0100 Subject: [PATCH] Minor guest account seed data changes --- api/src/database/createGuestAccount.ts | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git a/api/src/database/createGuestAccount.ts b/api/src/database/createGuestAccount.ts index edbb096..814d9e7 100644 --- a/api/src/database/createGuestAccount.ts +++ b/api/src/database/createGuestAccount.ts @@ -46,8 +46,10 @@ const seedIssues = (project: Project): Promise => { listPosition: 1, description: `

Your teams can collaborate in Jira applications by breaking down pieces of work into issues. Issues can represent tasks, software bugs, feature requests or any other type of project work.


Jira Software (software projects) issue types:


Bug 🐞

A bug is a problem which impairs or prevents the functions of a product.


Story 📗

A user story is the smallest unit of work that needs to be done.


Task 🗳

A task represents work that needs to be done.

`, estimate: 8, + timeSpent: 4, reporterId: users[1].id, project, + users: [users[0]], }), createEntity(Issue, { title: "Click on an issue to see what's behind it.", @@ -56,9 +58,11 @@ const seedIssues = (project: Project): Promise => { priority: IssuePriority.LOW, listPosition: 2, description: `

Key terms to know


Issues

A Jira 'issue' refers to a single work item of any type or size that is tracked from creation to completion. For example, an issue could be a feature being developed by a software team, a to-do item for a marketing team, or a contract that needs to be written by a legal team.


Projects

A project is, quite simply, a collection of issues that are held in common by purpose or context. Issues grouped into projects can be configured in a variety of ways, ranging from visibility restrictions to available workflows.


Workflows

Workflows represent the sequential path an issues takes from creation to completion. A basic workflow might look something like this:


Jira workflow diagram


In this case, Open, Done, and the labels in between represent the status an issue can take, while the arrows represent potential transitions from one status to another.


Agile

Agile is not a Jira Software-specific term. It's a work philosophy that originated in the software development field and has since expanded to a variety of other industries. While we won't belabor the definition here (there are great resources for that!), agile emphasizes an iterative approach to work informed by customer feedback where delivery occurs incrementally and continuously. The ideal agile team can move quickly and adapt to changing requirements without missing much of a beat.


Server

With Jira Software Server, you host Jira Software on your own hardware and customize your setup however you'd like. This is generally the best option for teams who need to manage all the details, have stricter requirements for data governance, and don't mind the additional complexity of hosting themselves.


Data Center


Data Center


With Jira Software Data Center, you can host Jira Software on your own hardware or with IaaS vendors like AWS and Azure. This is generally the best option for enterprise teams who need uninterrupted access to Jira Software and performance at scale.


`, - estimate: 40, + estimate: 5, + timeSpent: 2, reporterId: users[2].id, project, + users: [users[0]], }), createEntity(Issue, { title: 'Try dragging issues to different columns to transition their status.', @@ -68,9 +72,9 @@ const seedIssues = (project: Project): Promise => { listPosition: 3, description: `

An issue's status indicates its current place in the project's workflow. Here's a list of the statuses that come with JIRA products, depending on what projects you've created on your site.


Jira software issue statuses:


Backlog

The issue is waiting to be picked up in a future sprint.


Selected

The issue is open and ready for the assignee to start work on it.


In Progress

This issue is being actively worked on at the moment by the assignee.


Done

Work has finished on the issue.

`, estimate: 15, + timeSpent: 12, reporterId: users[1].id, project, - users: [users[2]], }), createEntity(Issue, { title: 'You can use rich text with images in issue descriptions.', @@ -80,6 +84,7 @@ const seedIssues = (project: Project): Promise => { listPosition: 4, description: `

🍏 🍎 🍐 🍊 🍋 🍌 🍉 🍇 🍓 🍈 🍒 🍑 🍍 🥭 🥥 🥝 🍅 🍆 🥑 🥦 🥒 🥬 🌶 🌽 🥕 🥔 🍠 🥐 🍞 🥖 🥨 🥯 🧀 🥚 🍳 🥞 🥓 🥩 🍗 🍖 🌭 🍔 🍟 🍕 🥪 🥙 🌮 🌯 🥗 🥘 🥫 🍝 🍜 🍲 🍛 🍣 🍱 🥟 🍤 🍙 🍚 🍘 🍥 🥮 🥠 🍢 🍡 🍧 🍨 🍦 🥧 🍰 🎂 🍮 🍭 🍬 🍫 🍿 🧂 🍩 🍪 🌰 🥜 🍯 🥛 🍼 ☕️ 🍵 🥤 🍶 🍺 🍻 🥂 🍷 🥃 🍸 🍹 🍾 🥄 🍴 🍽 🥣 🥡 🥢

`, estimate: 4, + timeSpent: 4, reporterId: users[0].id, project, users: [users[2]], @@ -91,7 +96,8 @@ const seedIssues = (project: Project): Promise => { priority: IssuePriority.HIGHEST, listPosition: 5, description: `

An issue's priority indicates its relative importance. The default priorities are listed below. Both the priorities and their meanings can be customized by your administrator to suit your organization. Learn more about configuring priorities and their descriptions.


Jira software issue priorities:


Highest ⬆️

This problem will block progress.


High ⬆️

Serious problem that could block progress.


Medium ⬆️

Has the potential to affect progress.


Low ⬇️

Minor problem or easily worked around.


Lowest ⬇️

Trivial problem with little or no impact on progress.

`, - estimate: 15, + estimate: 4, + timeSpent: 1, reporterId: users[2].id, project, }), @@ -102,7 +108,8 @@ const seedIssues = (project: Project): Promise => { priority: IssuePriority.HIGH, listPosition: 6, description: `

Try assigning Pickle Rick to this issue. 🥒 🥒 🥒


`, - estimate: 55, + estimate: 6, + timeSpent: 3, reporterId: users[1].id, project, users: [users[0], users[1]], @@ -116,6 +123,7 @@ const seedIssues = (project: Project): Promise => { listPosition: 7, description: `

Before you start work on an issue, you can set a time or other type of estimate to calculate how much work you believe it'll take to resolve it. Once you've started to work on a specific issue, log time to keep a record of it.


  • Open the issue and select ••• > Time tracking
  • Fill in the Time Spent field
  • Fill in the Time Remaining field and click Save


That's it!

💯💯

`, estimate: 12, + timeSpent: 11, reporterId: users[0].id, project, }), @@ -126,7 +134,8 @@ const seedIssues = (project: Project): Promise => { priority: IssuePriority.MEDIUM, listPosition: 7, description: `

Adding comments to an issue is a useful way to record additional detail about an issue, and collaborate with team members. Comments are shown in the Comments section when you view an issue.


  1. Open the issue on which to add your comment.
  2. Click the Add a comment button.
  3. (tick) Keyboard shortcut: m
  4. In the Comment text box, type your comment, using as many lines as you require. (tick) 
  5. Click the Save button to save the comment.
`, - estimate: 12, + estimate: 10, + timeSpent: 2, reporterId: users[0].id, project, users: [users[1]],