1
0

tips_tricks.rst 3.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120
  1. Tips and tricks
  2. ===============
  3. This page contains some tips and tricks on how to use pagure. These do not
  4. fit in their own page but are worth mentioning.
  5. Place image onto your overview page
  6. -----------------------------------
  7. You can only use images that come from the Pagure host itself.
  8. Example
  9. ~~~~~~~
  10. ::
  11. ![See Copr workflow](/copr/copr/raw/master/f/doc/img/copr-workflow.png)
  12. Text in the square brackets will be used as an alt description.
  13. Pre-fill issue using the URL
  14. ----------------------------
  15. When creating issues for a project pagure supports pre-filling the title
  16. and description input text using URL parameters.
  17. Example:
  18. ~~~~~~~~
  19. https://pagure.io/pagure/new_issue/?title=<Issue>&content=<Issue Content>
  20. The above URL will autofill the text boxes for Title and Description field
  21. with Title set to <Issue> and Description set to <Issue Content>.
  22. Pre-fill issue template using the URL
  23. -------------------------------------
  24. When creating issues for a project pagure supports pre-filling the title
  25. and description input text using URL parameters.
  26. Example:
  27. ~~~~~~~~
  28. https://pagure.io/pagure/new_issue/?template=<TemplateName>
  29. The above URL will autofill the ticket with the specified template. The
  30. TemplateName should be the name of the template file on disk (in the
  31. ``templates`` directory of the ticket git repository).
  32. Filter for issues *not* having a certain tag
  33. --------------------------------------------
  34. Very much in the same way pagure allows you to filter for issues having a
  35. certain tag, pagure allows one to filter for issues *not* having a certain tag.
  36. To do this, simply prepend a ``!`` in front of the tag.
  37. Example:
  38. ~~~~~~~~
  39. https://pagure.io/pagure/issues?tags=!easyfix
  40. Local user creation without email verification
  41. ----------------------------------------------
  42. If you set ``EMAIL_SEND`` to ```False``` from the configuration file, you
  43. will get the emails printed to the console instead of being sent. The admin
  44. of the instance can then access the URL to manually validate the account from
  45. there. This is generally used for development where we don't need to send
  46. any emails.
  47. Filter an user's projects by their access
  48. -----------------------------------------
  49. When watching a user's page, the list of all the project that user is
  50. involved in is presented regardless of whether the user has ticket, commit,
  51. admin access or is the main admin of the project.
  52. You can specify an ``acl=`` argument to the URL to filter the list of
  53. projects by access.
  54. .. note:: This also works for your home page when you are logged in.
  55. Examples:
  56. ~~~~~~~~~
  57. https://pagure.io/user/pingou?acl=main admin
  58. https://pagure.io/user/pingou?acl=admin
  59. https://pagure.io/user/pingou?acl=commit
  60. Filter issues by (custom) fields
  61. --------------------------------
  62. Via the project's settings page, admins can set custom keys to be used in
  63. issues. You can search them using the URL via the arguments ``ckeys`` and
  64. ``cvalue`` or simpler, using the search field at the top of the issue page.
  65. This also works for the following regular fields: ``tags``, ``milestones``,
  66. ``author``, ``assignee``, ``status``, ``priority`` (but tags and milestones
  67. despite their name only support a single value).
  68. Examples:
  69. ~~~~~~~~~
  70. https://pagure.io/SSSD/sssd/issues?status=Open&search_pattern=review%3ATrue
  71. https://pagure.io/pagure/issues?status=Open&search_pattern=tags%3Aeasyfix
  72. Search the comments of issues
  73. -----------------------------
  74. One can search all the comments made on an issue tracker using
  75. ``content:<keyword>`` in the search field. This is going to search all the
  76. comments (including the descriptions) of all the tickets and thus can be quite
  77. slow on large project. This is why this feature isn't being pushed much forward.
  78. Examples:
  79. ~~~~~~~~~
  80. https://pagure.io/pagure/issues?status=Open&search_pattern=content%3Aeasyfix