Summary Files Commits Branches @commit @diff @stats
path: root / src / tutorials
diff options
context:
space:
mode:
Commit75574c193a22373bf13d2afc0f65c4eece150697 (patch)
Author
 Syndamia <kamen.d.mladenov@protonmail.com>
2021-03-12 09:33:17 +0200
Committer
 Syndamia <kamen.d.mladenov@protonmail.com>
2021-03-12 09:33:17 +0200
Files68d00260a9e223920c6bcadb57b11c6d8d41f945 /src/tutorials
syndamia.com-75574c193a22373bf13d2afc0f65c4eece150697.tar
syndamia.com-75574c193a22373bf13d2afc0f65c4eece150697.tar.gz
syndamia.com-75574c193a22373bf13d2afc0f65c4eece150697.zip
Parent8e85299a3f5b9289a7e9d7e67e3a2bc8d550c5cb (diff)
Updated header links in all files
diff --git a/src/tutorials/connect-to-mysql-in-csharp-ef/connecting.md b/src/tutorials/connect-to-mysql-in-csharp-ef/connecting.md
index 6f05a76..61989f4 100644
--- a/src/tutorials/connect-to-mysql-in-csharp-ef/connecting.md
+++ b/src/tutorials/connect-to-mysql-in-csharp-ef/connecting.md
@@ -1,5 +1,5 @@
# Connect to MySql in C# and Entity Framework - Connecting
-[🔗](#Connect%20to%20MySql%20in%20C#%20and%20Entity%20Framework%20-%20Connecting)
+[![🔗](/img/link-tabler.svg)](#Connect%20to%20MySql%20in%20C#%20and%20Entity%20Framework%20-%20Connecting)
**Article Created: 21 May 2020** || **Last Edited: 25 November 2020**
@@ -8,7 +8,7 @@
---
## Connection string
-[🔗](#Connection%20string)
+[![🔗](/img/link-tabler.svg)](#Connection%20string)
You can find a truckload of ways to make your connection string from places like [this](https://www.connectionstrings.com/mysql/) but in this case, I've found out that most don't work.
After a lot of trial and error, I've found that this one works the best:
@@ -22,7 +22,7 @@ If you are using `MySQL Workbench` and you don't know your port and id, you can
![MyServer root 127.0.0.1:3306](./img/connections.png) In this example, the user id is _root_ and the port is _3306_.
## ASP.NET Startup
-[🔗](#ASP.NET%20Startup)
+[![🔗](/img/link-tabler.svg)](#ASP.NET%20Startup)
If you are making an `ASP.NET` application, you'll need to put the connection string in the `ConfigureServices` method of the `Startup.cs` file.
@@ -44,7 +44,7 @@ public void ConfigureServices(IServiceCollection services)
```
## DBContext child class
-[🔗](#DBContext%20child%20class)
+[![🔗](/img/link-tabler.svg)](#DBContext%20child%20class)
If you want to connect a `DBContext` child class to a `MySQL` database, one of the easiest ways to do it, is to override the `OnConfiguring` method.
diff --git a/src/tutorials/connect-to-mysql-in-csharp-ef/introduction.md b/src/tutorials/connect-to-mysql-in-csharp-ef/introduction.md
index b17c772..b6e3a6e 100644
--- a/src/tutorials/connect-to-mysql-in-csharp-ef/introduction.md
+++ b/src/tutorials/connect-to-mysql-in-csharp-ef/introduction.md
@@ -1,5 +1,5 @@
# Connect to MySql in C# and Entity Framework - Introduction
-[🔗](#Connect%20to%20MySql%20in%20C#%20and%20Entity%20Framework%20-%20Introduction)
+[![🔗](/img/link-tabler.svg)](#Connect%20to%20MySql%20in%20C#%20and%20Entity%20Framework%20-%20Introduction)
**Article Created: 21 May 2020** || **Last Edited: 25 November 2020**
@@ -10,7 +10,7 @@
In my experience, connecting a `C#` application to a `MySQL` database with Entity Framework can be quite tricky. Here, I share what works for me.
## Contents
-[🔗](#Contents)
+[![🔗](/img/link-tabler.svg)](#Contents)
1. [Introduction](./introduction.html)
2. [Preparation](./preparation.html)
diff --git a/src/tutorials/connect-to-mysql-in-csharp-ef/preparation.md b/src/tutorials/connect-to-mysql-in-csharp-ef/preparation.md
index 4383454..f7ab5ca 100644
--- a/src/tutorials/connect-to-mysql-in-csharp-ef/preparation.md
+++ b/src/tutorials/connect-to-mysql-in-csharp-ef/preparation.md
@@ -1,5 +1,5 @@
# Connect to MySql in C# and Entity Framework - Preparation
-[🔗](#Connect%20to%20MySql%20in%20C#%20and%20Entity%20Framework%20-%20Preparation)
+[![🔗](/img/link-tabler.svg)](#Connect%20to%20MySql%20in%20C#%20and%20Entity%20Framework%20-%20Preparation)
**Article Created: 21 May 2020** || **Last Edited: 25 November 2020**
@@ -8,12 +8,12 @@
---
## MySql
-[🔗](#MySql)
+[![🔗](/img/link-tabler.svg)](#MySql)
This tutorial doesn't cover it, but you'll need to have properly [installed and configured](https://dev.mysql.com/doc/mysql-installation-excerpt/5.7/en/) `MySQL`.
## NuGet packages
-[🔗](#NuGet%20packages)
+[![🔗](/img/link-tabler.svg)](#NuGet%20packages)
You'll need to install two NuGet packages: [Microsoft.EntityFrameworkCore](https://www.nuget.org/packages/Microsoft.EntityFrameworkCore) and [MySql.Data.EntityFrameworkCore](https://www.nuget.org/packages/MySql.Data.EntityFrameworkCore/).
diff --git a/src/tutorials/how-to-use-jira/bug.md b/src/tutorials/how-to-use-jira/bug.md
index a5d1711..342bdb9 100644
--- a/src/tutorials/how-to-use-jira/bug.md
+++ b/src/tutorials/how-to-use-jira/bug.md
@@ -1,5 +1,5 @@
# How to use Jira - Bug tracking template
-[🔗](#How%20to%20use%20Jira%20-%20Bug%20tracking%20template)
+[![🔗](/img/link-tabler.svg)](#How%20to%20use%20Jira%20-%20Bug%20tracking%20template)
**Article Created: 24 July 2020** || **Last Edited: 16 September 2020**
diff --git a/src/tutorials/how-to-use-jira/cards.md b/src/tutorials/how-to-use-jira/cards.md
index 6712a02..c84005e 100644
--- a/src/tutorials/how-to-use-jira/cards.md
+++ b/src/tutorials/how-to-use-jira/cards.md
@@ -1,5 +1,5 @@
# How to use Jira - Cards
-[🔗](#How%20to%20use%20Jira%20-%20Cards)
+[![🔗](/img/link-tabler.svg)](#How%20to%20use%20Jira%20-%20Cards)
**Article Created: 24 July 2020** || **Last Edited: 12 September 2020**
@@ -12,7 +12,7 @@
![](./img/kanban-cards.png)
## Properties
-[🔗](#Properties)
+[![🔗](/img/link-tabler.svg)](#Properties)
Each card has the following properties:
@@ -61,14 +61,14 @@ Each card has the following properties:
![](./img/epic-link-create-card.png)
## Creating
-[🔗](#Creating)
+[![🔗](/img/link-tabler.svg)](#Creating)
To create a card yourself, you need to **press the `Create` button on the top bar**.
![](./img/create-header.png)
## Viewing
-[🔗](#Viewing)
+[![🔗](/img/link-tabler.svg)](#Viewing)
**All** cards (issues) can be viewed from a [project](./projects.html)'s side menu, under 'Issues'.
@@ -77,7 +77,7 @@ To create a card yourself, you need to **press the `Create` button on the top ba
Of course, they can also be viewed through **[filters](./filters.html)** and a **[project](./projects.html)'s board**.
## How to use
-[🔗](#How%20to%20use)
+[![🔗](/img/link-tabler.svg)](#How%20to%20use)
By default, opening a card presents, at the top, it's **key** (think of it as an ID),
@@ -108,7 +108,7 @@ and **work logs** (a bit later we talk about them in more detail).
![](./img/activity-work-log.png)
### Right side
-[🔗](#Right%20side)
+[![🔗](/img/link-tabler.svg)](#Right%20side)
To the right side, you have all of the different **properties** (some fields without a value will be hidden).
@@ -125,7 +125,7 @@ On the top right you can change **watch options** ([watching an issue](https://w
The most notable options are [`Log work`](https://confluence.atlassian.com/jirasoftwarecloud/logging-work-on-issues-902499028.html) and `Add flag`.
### Work log
-[🔗](#Work%20log)
+[![🔗](/img/link-tabler.svg)](#Work%20log)
In Jira, you can **estimate how long an issue will take for it to be resolved**. This is done through **logging work**.
@@ -136,14 +136,14 @@ In the `Log work` screen, you'll be met with a `Time spent` and `Time remaining`
The time remaining takes a **default** value from the **previous time log**, so you don't need to specify it every time.
### Issue flagging
-[🔗](#Issue%20flagging)
+[![🔗](/img/link-tabler.svg)](#Issue%20flagging)
A **flagged issue** is an issue that is very important. Flagged issues are displayed in yellow to signify their needed attention.
![](./img/flagged-card.png)
### Basic issue information
-[🔗](#Basic issue information)
+[![🔗](/img/link-tabler.svg)](#Basic issue information)
On the bottom right you can see **when the issue was created** and **when it was last updated**. You can also access the field configuration menu from the `Configure` button. It won't be covered in this tutorial, you can read about it [here](https://confluence.atlassian.com/adminjiracloud/changing-a-field-configuration-844500798.html).
diff --git a/src/tutorials/how-to-use-jira/components.md b/src/tutorials/how-to-use-jira/components.md
index ac3d4e4..a2ed420 100644
--- a/src/tutorials/how-to-use-jira/components.md
+++ b/src/tutorials/how-to-use-jira/components.md
@@ -1,5 +1,5 @@
# How to use Jira - Components
-[🔗](#How%20to%20use%20Jira%20-%20Components)
+[![🔗](/img/link-tabler.svg)](#How%20to%20use%20Jira%20-%20Components)
**Article Created: 24 July 2020** || **Last Edited: 16 September 2020**
@@ -10,7 +10,7 @@
Components are **yet another way to group issues together**. They don't have any specific meaning like versions, their usage depends on the project's organisation.
## Creating and editing
-[🔗](#Creating%20and%20editing)
+[![🔗](/img/link-tabler.svg)](#Creating%20and%20editing)
Creating and editing them is done from the **`Components` menu in the sidebar**.
@@ -29,7 +29,7 @@ Clicking on it presents you with a screen where you input it's information.
**A name is the only requirement**. You can also add a **description**, **a lead(er) for the component** and **person who gets assigned to an issue by default**.
## Adding issues
-[🔗](#Adding%20issues)
+[![🔗](/img/link-tabler.svg)](#Adding%20issues)
Adding an issue to a component can be done either **when creating it** or **when viewing it**.
diff --git a/src/tutorials/how-to-use-jira/dashboards.md b/src/tutorials/how-to-use-jira/dashboards.md
index ba99293..a890ce5 100644
--- a/src/tutorials/how-to-use-jira/dashboards.md
+++ b/src/tutorials/how-to-use-jira/dashboards.md
@@ -1,5 +1,5 @@
# How to use Jira - Dashboards
-[🔗](#How%20to%20use%20Jira%20-%20Dashboards)
+[![🔗](/img/link-tabler.svg)](#How%20to%20use%20Jira%20-%20Dashboards)
**Article Created: 24 July 2020** || **Last Edited: 16 September 2020**
@@ -18,7 +18,7 @@ Dashboards are composed of **gadgets**.
Gadgets have functionality for **displaying certain information**, like `Average Age Chart` or `Issues in progress`. Each gadget can be setup to **take information from one or more projects and/or saved filters**.
## Adding a dashboard
-[🔗](#Adding%20a%20dashboard)
+[![🔗](/img/link-tabler.svg)](#Adding%20a%20dashboard)
Dashboard can be added from the top bar, under `Create dashboard` in the `Dashboards` menu
@@ -29,7 +29,7 @@ or, if you are already in a dashboard, from `Create dashboard` in the three dots
![](./img/create-dashboard-dots.png)
## Adding gadgets
-[🔗](#Adding%20gadgets)
+[![🔗](/img/link-tabler.svg)](#Adding%20gadgets)
**Note**: you cannot add gadgets to the default dashboard.
diff --git a/src/tutorials/how-to-use-jira/filters.md b/src/tutorials/how-to-use-jira/filters.md
index de95525..32aa2ff 100644
--- a/src/tutorials/how-to-use-jira/filters.md
+++ b/src/tutorials/how-to-use-jira/filters.md
@@ -1,5 +1,5 @@
# How to use Jira - Filters
-[🔗](#How%20to%20use%20Jira%20-%20Filters)
+[![🔗](/img/link-tabler.svg)](#How%20to%20use%20Jira%20-%20Filters)
**Article Created: 23 July 2020** || **Last Edited: 11 September 2020**
@@ -14,7 +14,7 @@ Making filters is done through the `Advanced issue search` page, from the `Filte
![](./img/filters-advanced-issue-search.png)
## Criteria
-[🔗](#Criteria)
+[![🔗](/img/link-tabler.svg)](#Criteria)
From here you can see some criteria: `Project`, `Type`, `Status`, `Assignee`.
@@ -34,7 +34,7 @@ You can view all of your filters from the conveniently named `View all filters`
![](./img/view-all-filters-advanced-issue-search.png)
## JQL
-[🔗](#JQL)
+[![🔗](/img/link-tabler.svg)](#JQL)
You can do **more advanced search** through `JQL` (Jira Query Language), but we won't be covering this topic. I can recommend [this article](https://www.atlassian.com/blog/jira-software/jql-the-most-flexible-way-to-search-jira-14) on the subject.
diff --git a/src/tutorials/how-to-use-jira/introduction.md b/src/tutorials/how-to-use-jira/introduction.md
index 14852a8..77a695c 100644
--- a/src/tutorials/how-to-use-jira/introduction.md
+++ b/src/tutorials/how-to-use-jira/introduction.md
@@ -1,5 +1,5 @@
# How to use Jira - Introduction
-[🔗](#How%20to%20use%20Jira%20-%20Introduction)
+[![🔗](/img/link-tabler.svg)](#How%20to%20use%20Jira%20-%20Introduction)
**Article Created: 23 July 2020** || **Last Edited: 11 September 2020**
@@ -14,7 +14,7 @@ It has a lot of features that can be quite overwhelming for new comers, especial
**Note**: certain actions can be done only from a project administrator
## Contents
-[🔗](#Contents)
+[![🔗](/img/link-tabler.svg)](#Contents)
1. [Introduction](./introduction.md)
2. [Filters](./filters.html)
diff --git a/src/tutorials/how-to-use-jira/kanban.md b/src/tutorials/how-to-use-jira/kanban.md
index c08dec7..f82a0a9 100644
--- a/src/tutorials/how-to-use-jira/kanban.md
+++ b/src/tutorials/how-to-use-jira/kanban.md
@@ -1,5 +1,5 @@
# How to use Jira - Kanban template
-[🔗](#How%20to%20use%20Jira%20-%20Kanban%20template)
+[![🔗](/img/link-tabler.svg)](#How%20to%20use%20Jira%20-%20Kanban%20template)
**Article Created: 23 July 2020** || **Last Edited: 16 September 2020**
@@ -14,7 +14,7 @@ In a projects that uses the kanban template, boards can access directly all of t
This tutorial focuses on the basics, but you can find a lot of information in [these sets of articles](https://www.atlassian.com/agile/kanban) from Atlassian.
## Create board
-[🔗](#Create%20board)
+[![🔗](/img/link-tabler.svg)](#Create%20board)
This template can be chosen when **creating a project**
@@ -25,7 +25,7 @@ and **from the `Create board` screen**.
![](./img/scrum-kanban-board.png)
## Backlog
-[🔗](#Backlog)
+[![🔗](/img/link-tabler.svg)](#Backlog)
In kanban, **the backlog is just another column in your board(s)**. It can be removed entirely.
diff --git a/src/tutorials/how-to-use-jira/pages.md b/src/tutorials/how-to-use-jira/pages.md
index fb03c28..6b2ef48 100644
--- a/src/tutorials/how-to-use-jira/pages.md
+++ b/src/tutorials/how-to-use-jira/pages.md
@@ -1,5 +1,5 @@
# How to use Jira - Pages
-[🔗](#How%20to%20use%20Jira%20-%20Pages)
+[![🔗](/img/link-tabler.svg)](#How%20to%20use%20Jira%20-%20Pages)
**Article Created: 24 July 2020** || **Last Edited: 16 September 2020**
diff --git a/src/tutorials/how-to-use-jira/projects.md b/src/tutorials/how-to-use-jira/projects.md
index fa49bac..36666a6 100644
--- a/src/tutorials/how-to-use-jira/projects.md
+++ b/src/tutorials/how-to-use-jira/projects.md
@@ -1,5 +1,5 @@
# How to use Jira - Projects
-[🔗](#How%20to%20use%20Jira%20-%20Projects)
+[![🔗](/img/link-tabler.svg)](#How%20to%20use%20Jira%20-%20Projects)
**Article Created: 23 July 2020** || **Last Edited: 12 September 2020**
@@ -12,7 +12,7 @@
In short, **projects are a collection of issues** with added functionality for **organising them, getting statistics, etc**.
## Creating a project
-[🔗](#Creating%20a%20project)
+[![🔗](/img/link-tabler.svg)](#Creating%20a%20project)
To create a project, either **click on `Create project` from the menu `Projects` in the top bar**,
@@ -43,12 +43,12 @@ In a nutshell, **templates** govern how **boards and issues should work together
Projects also have [Releases](./releases.html), [Pages](./pages.html) and [Components](./components.html), that are also explored.
## Boards
-[🔗](#Boards)
+[![🔗](/img/link-tabler.svg)](#Boards)
Each project contains, amongst many other things, boards. **Boards are a way to better organise results from [filters](./filters.html)**. By default every project gets a board with a filter for all of the project's issues.
### Columns
-[🔗](#Columns)
+[![🔗](/img/link-tabler.svg)](#Columns)
**Boards are divided into columns** that contain the cards (issues). A card can move **freely** from one column to another.
@@ -69,7 +69,7 @@ Adding and removing columns can be done from the `Columns` tab in the `Board set
![](./img/columns-edit.png)
### Adding more boards to a project
-[🔗](#Adding%20more%20boards%20to%20a%20project)
+[![🔗](/img/link-tabler.svg)](#Adding%20more%20boards%20to%20a%20project)
You can also add to a project as many [**Scrum**](./scrum.html) and [**Kanban**](./kanban.html) templated boards as you want.
@@ -102,7 +102,7 @@ Once you've made your choice, you will be met with three options:
![](./img/ntb-filter.png)
## Backlog
-[🔗](#Backlog)
+[![🔗](/img/link-tabler.svg)](#Backlog)
**The backlog is a place for issues that outline a general task/feature**.
@@ -119,7 +119,7 @@ or **nonexistent ([bug tracking](./bug.md))**.
The purpose of the backlog depends on the template and it is described in the page of each template.
## Add item
-[🔗](#Add%20item)
+[![🔗](/img/link-tabler.svg)](#Add%20item)
**You can also add some resources to the sidebar of your project** for everyone to use. That is done through the `Add Item` menu.
diff --git a/src/tutorials/how-to-use-jira/releases.md b/src/tutorials/how-to-use-jira/releases.md
index e3dfa78..fb51969 100644
--- a/src/tutorials/how-to-use-jira/releases.md
+++ b/src/tutorials/how-to-use-jira/releases.md
@@ -1,5 +1,5 @@
# How to use Jira - Releases
-[🔗](#How%20to%20use%20Jira%20-%20Releases)
+[![🔗](/img/link-tabler.svg)](#How%20to%20use%20Jira%20-%20Releases)
**Article Created: 24 July 2020** || **Last Edited: 16 September 2020**
@@ -12,7 +12,7 @@ The `Releases` page in a project shows **versions**, the ones in development and
**Versions are just a big collection of issues** and the **goal of a released version** is for **all of it's issues to be resolved**. It serves as a point in time for the development of a project.
## Adding issues to a version
-[🔗](#Adding%20issues%20to%20a%20version)
+[![🔗](/img/link-tabler.svg)](#Adding%20issues%20to%20a%20version)
When creating an issue, you can specify a version in the `Fix versions` property.
diff --git a/src/tutorials/how-to-use-jira/scrum.md b/src/tutorials/how-to-use-jira/scrum.md
index 4da32cd..7321b44 100644
--- a/src/tutorials/how-to-use-jira/scrum.md
+++ b/src/tutorials/how-to-use-jira/scrum.md
@@ -1,5 +1,5 @@
# How to use Jira - Scrum template
-[🔗](#How%20to%20use%20Jira%20-%20Scrum%20template)
+[![🔗](/img/link-tabler.svg)](#How%20to%20use%20Jira%20-%20Scrum%20template)
**Article Created: 24 July 2020** || **Last Edited: 16 September 2020**
@@ -16,7 +16,7 @@ In general [agile software development](https://www.atlassian.com/agile), a **sp
Your **boards only work on the issues of the currently active sprint**.
## Backlog
-[🔗](#Backlog)
+[![🔗](/img/link-tabler.svg)](#Backlog)
As we've discussed, the **backlog** is used for organising **all issues** into **sprints**.
@@ -31,14 +31,14 @@ Creating a sprint is done from the conveniently named `Create sprint` button. It
![](./img/sample-sprint.png)
## Boards and Issues
-[🔗](#Boards%20and%20Issues)
+[![🔗](/img/link-tabler.svg)](#Boards%20and%20Issues)
As previously mentioned, boards have access only to the issues in the active sprint. This is also reflected in the user interface. After selecting a board from the sidebar, you view it from the `Active sprints` page.
![](./img/active-sprints.png)
## Create board
-[🔗](#Create%20board)
+[![🔗](/img/link-tabler.svg)](#Create%20board)
This template can be chosen when **creating a project**