Patch #28138

Add link to add a new issue on the version page

Added by Holger Just about 1 month ago. Updated 26 days ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:


Target version:Candidate for next major release


When showing a single version, a common task is to edit issues there. For existing issues, users can easily use the context menu for that. To add issues however requires a rather complex workflow to go to the "new issue" page, select the version and create the issue.

The attached patch against the current trunk at r17192 adds a new link to the show page of a single version to directly add a new issue for that version in the version's project. It links to a pre-configured add-issue form. The patch was extracted from Planio.

0001-Add-New-issue-button-on-version-show-page.patch Magnifier (1.65 KB) Holger Just, 2018-02-05 17:23

Related issues

Duplicated by Redmine - Feature #5005: "New issue" link near roadmap issue lists. Closed 2010-03-07


#1 Updated by Go MAEDA about 1 month ago

  • Duplicated by Feature #5005: "New issue" link near roadmap issue lists. added

#2 Updated by Marius BALTEANU about 1 month ago

Really nice improvement.

I think that we need some tests to cover the cases when the "Add issue" button should be shown or not. @Holger, if you can't add them, I can do it in the next weeks.

#3 Updated by Go MAEDA 27 days ago

  • Target version set to Candidate for next major release

I really like this improvement. In fact, I posted a similar patch #5005#note-6 years ago.

But I noticed that the "New issue" link is displayed even if the version is locked or closed. I think it would be better to check the status of the version when showing the link.

#4 Updated by Mischa The Evil 26 days ago

I'm just reading along – visually scanning the patches, while being aware of #5005. Nevertheless, I wanted to drop a thought regarding this patch.

In addition to the thing mentioned by Go in the previous note, the patch also doesn't seem to consider (at least) one of the two cases that Jean-Philippe mentioned in #5005#note-8, namely the possibility that the target version field may be read-only for the user. I am not entirely sure that the second case (target version field being not available for the default tracker) is properly covered by this patch, though. It looks like it, but I'd need to test that specifically.

Despite all the difficulties, I do like the actual proposal (just like I liked #5005).

Also available in: Atom PDF