#2601 Issue Templates needs updates
Closed: Fixed 7 years ago Opened 7 years ago by bex.

https://docs.pagure.org/pagure/usage/ticket_templates.html

It should be noted that the MD is not processed as markdown - specifically this means that questions do not get auto-numbered.

It should be noted that there are rules for the names of templates. It appears that templates that start with a number do not work.

i.e. 2018-bid.md shows in the list as 2018-b and won't load.


It should be noted that the MD is not processed as markdown - specifically this means that questions do not get auto-numbered.

Not sure I'm following you here.

It should be noted that there are rules for the names of templates. It appears that templates that start with a number do not work.

This surprises me but I never tried it will need to :)

i.e. 2018-bid.md shows in the list as 2018-b and won't load.

Is this related to the point you raised above or do you think it's something else?

Alright, so the file name issue has been figured out as well as another issue, it seems the endpoint to load template was not taking namespacing into account, so I guess you're the first one to use this feature on a namespaced project :)

Metadata Update from @pingou:
- Issue assigned to pingou

7 years ago

Metadata Update from @pingou:
- Assignee reset

7 years ago

Metadata Update from @pingou:
- Issue assigned to pingou
- Issue tagged with: bug

7 years ago

I don't think I used a namespace for this project - now I am worried :)

Also, the docs reference that all of the repos are listed on the overview page. They aren't. Lastly, I just remembered that the example of how to find your ticket repo is actually incorrect. The text and the example do not agree.

I don't think I used a namespace for this project - now I am worried :)

Well, I don't know which project you had/have the issue with :)

Also, the docs reference that all of the repos are listed on the overview page. They aren't. Lastly, I just remembered that the example of how to find your ticket repo is actually incorrect. The text and the example do not agree.

A little more context for these would be nice, I'm really not sure I understand what you are referring to. Are these points related to the issue at hand on this ticket or are they new issues?

I don't think I used a namespace for this project - now I am worried :)
Well, I don't know which project you had/have the issue with :)

Fair point :)

Also, the docs reference that all of the repos are listed on the overview page. They aren't. Lastly, I just remembered that the example of how to find your ticket repo is actually incorrect. The text and the example do not agree.
A little more context for these would be nice, I'm really not sure I understand what you are referring to. Are these points related to the issue at hand on this ticket or are they new issues?

Same page, so same issue, imho.

From the page:

For a project named test on pagure.io.
First, clone the ticket git repo [1] and move into it
git clone ssh://git@pagure.io/tickets/pagure.git
cd test

I believe that should actually read

git clone ssh://git@pagure.io/tickets/test.git

The above quoted text contains reference to this footnote:

[1] All the URLs to the different git repositories can be found on the main page of the project, on the right-side menu, under the section Source GIT URLs, click on more to see them.

I do not believe the repos are all listed. At least I can't find them.

The above quoted text contains reference to this footnote:

[1] All the URLs to the different git repositories can be found on the main page of the project, on the right-side menu, under the section Source GIT URLs, click on more to see them.

I do not believe the repos are all listed. At least I can't find them.

They should be there with two conditions: a) you are logged in and b) you have access to the repo (which means commit access or higher). We should adjust the documentation to mention this I guess :)

Is the adjustment made in https://pagure.io/pagure/pull-request/2602 corresponding to what you had in mind?

The above quoted text contains reference to this footnote:

[1] All the URLs to the different git repositories can be found on the main page of the project, on the right-side menu, under the section Source GIT URLs, click on more to see them.

I do not believe the repos are all listed. At least I can't find them.

They should be there with two conditions: a) you are logged in and b) you have access to the repo (which means commit access or higher). We should adjust the documentation to mention this I guess :)

We should mention this. I also learned today that I have to actually click "more" and not dream I did :)

Is the adjustment made in https://pagure.io/pagure/pull-request/2602 corresponding to what you had in mind?

Commented in PR

Commit 91c1f35 relates to this ticket

Log in to comment on this ticket.

Metadata