From 4d0423cd9fd3eb62a8d61881ea8a02322eef4a4d Mon Sep 17 00:00:00 2001 From: karen Carias Date: Tue, 25 Aug 2015 22:15:02 -0700 Subject: New doc about how to create an issue --- doc/gitlab-basics/README.md | 2 ++ doc/gitlab-basics/create-issue.md | 27 +++++++++++++++++++++++++++ 2 files changed, 29 insertions(+) create mode 100644 doc/gitlab-basics/create-issue.md diff --git a/doc/gitlab-basics/README.md b/doc/gitlab-basics/README.md index b904c70e980..493e1d1b09c 100644 --- a/doc/gitlab-basics/README.md +++ b/doc/gitlab-basics/README.md @@ -23,3 +23,5 @@ Step-by-step guides on the basics of working with Git and GitLab. * [Add an image](add-image.md) * [Create a Merge Request](add-merge-request.md) + +* [Create an Issue](create-issue.md) diff --git a/doc/gitlab-basics/create-issue.md b/doc/gitlab-basics/create-issue.md new file mode 100644 index 00000000000..a272e84d4f3 --- /dev/null +++ b/doc/gitlab-basics/create-issue.md @@ -0,0 +1,27 @@ +# How to create an Issue in GitLab + +The Issue Tracker is a good place to add things that need to be improved or solved in a project. + +To create an Issue, sign in to GitLab. + +Go to the project where you'd like to create the Issue: + +![Select a project](basicsimages/select_project.png) + +Click on "Issues" on the left side of your screen: + +![Issues](basicsimages/issues.png) + +Click on the "+ new issue" button on the right side of your screen: + +![New issue](basicsimages/new_issue.png) + +Add a title and a description to your issue: + +![Issue title and description](basicsimages/issue_title.png) + +You may assign the Issue to a user, add a milestone and add labels (they are all optional). Then click on "submit new issue": + +![Submit new issue](basicsimages/submit_new_issue.png) + +Your Issue will now be added to the Issue Tracker and will be ready to be reviewed. -- cgit v1.2.1 From 92e15cfb82620ff85558d4a8f1a5b84dacabcab4 Mon Sep 17 00:00:00 2001 From: karen Carias Date: Mon, 31 Aug 2015 23:01:25 -0700 Subject: more info about MR and mentions --- doc/gitlab-basics/create-issue.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/gitlab-basics/create-issue.md b/doc/gitlab-basics/create-issue.md index a272e84d4f3..87f078def04 100644 --- a/doc/gitlab-basics/create-issue.md +++ b/doc/gitlab-basics/create-issue.md @@ -24,4 +24,4 @@ You may assign the Issue to a user, add a milestone and add labels (they are all ![Submit new issue](basicsimages/submit_new_issue.png) -Your Issue will now be added to the Issue Tracker and will be ready to be reviewed. +Your Issue will now be added to the Issue Tracker and will be ready to be reviewed. You can comment on it and mention the people involved. You can also link Issues to the Merge Requests where the Issues are solved. To do this, you can use an [Issue closing pattern](http://doc.gitlab.com/ce/customization/issue_closing.html). -- cgit v1.2.1 From 4743b8bd6a6c1556c1a3163b438de90360e2e374 Mon Sep 17 00:00:00 2001 From: karen Carias Date: Tue, 8 Sep 2015 18:36:11 -0700 Subject: link to rake tasks --- doc/raketasks/backup_restore.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/doc/raketasks/backup_restore.md b/doc/raketasks/backup_restore.md index 6a68c8e8286..b0ea1a97535 100644 --- a/doc/raketasks/backup_restore.md +++ b/doc/raketasks/backup_restore.md @@ -7,7 +7,9 @@ A backup creates an archive file that contains the database, all repositories and all attachments. This archive will be saved in backup_path (see `config/gitlab.yml`). The filename will be `[TIMESTAMP]_gitlab_backup.tar`. This timestamp can be used to restore an specific backup. -You can only restore a backup to exactly the same version of GitLab that you created it on, for example 7.2.1. The best way to migrate your repositories from one server to another is through backup restore. +You can only restore a backup to exactly the same version of GitLab that you created it +on, for example 7.2.1. The best way to migrate your repositories from one server to +another is through backup restore. You need to keep a separate copy of `/etc/gitlab/gitlab-secrets.json` (for omnibus packages) or `/home/git/gitlab/.secret` (for installations @@ -370,3 +372,6 @@ For more information see similar questions on postgresql issue tracker[here](htt ## Note This documentation is for GitLab CE. We backup GitLab.com and make sure your data is secure, but you can't use these methods to export / backup your data yourself from GitLab.com. + +To migrate your repositories from one server to another with an up-to-date version of +GitLab, you can use [rake tasks](import.md) to do a mass import of the repository. -- cgit v1.2.1 From 6a1d695f861e4c5251a2333c673f78705b34891f Mon Sep 17 00:00:00 2001 From: karen Carias Date: Wed, 9 Sep 2015 15:17:41 -0700 Subject: made info more clear --- doc/raketasks/backup_restore.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/raketasks/backup_restore.md b/doc/raketasks/backup_restore.md index b0ea1a97535..ad1914398d6 100644 --- a/doc/raketasks/backup_restore.md +++ b/doc/raketasks/backup_restore.md @@ -374,4 +374,6 @@ This documentation is for GitLab CE. We backup GitLab.com and make sure your data is secure, but you can't use these methods to export / backup your data yourself from GitLab.com. To migrate your repositories from one server to another with an up-to-date version of -GitLab, you can use [rake tasks](import.md) to do a mass import of the repository. +GitLab, you can use the [import rake task](import.md) to do a mass import of the +repository. Note that if you do an import rake task, rather than a backup restore, you +will have all your repositories, but not any other data. -- cgit v1.2.1