#2966 Expose related artifacts on commits and blog posts

v1.0.0
closed
sf-2 (994)
General
nobody
2015-08-20
2011-10-10
No

We already show related artifacts on tickets, blog posts, comments, etc. But we should for blog posts and commits too.

Discussion

  • Dave Brondsema

    Dave Brondsema - 2012-01-06
    • size: --> 2
     
    • status: open --> in-progress
    • assigned_to: Tim Van Steenburgh
     
    • status: in-progress --> code-review
    • qa: Jenny Steele
     
  • forge:tv/2966

    The 'commit' part of this ticket was moved to [#3821].

    QA: Install Tracker tool and make a ticket. Install Blog tool, make a post, and put [#1] in the post content. Save. Make sure the Related Artifacts section appears under the post with a link to the Tracker ticket. Click through to the ticket and make sure there's a link back to the blog post.

     

    Related

    Tickets: #3821

  • Jenny Steele - 2012-02-29

    Works, but a test would be good. You could probably just adapt test_related_artifacts in the tracker tests.

     
  • Jenny Steele - 2012-02-29
    • status: code-review --> open
     
  • To ssh://engr.geek.net/forge
    4f3305b..eb216c7 tv/2966 -> tv/2966

    Added functional test.

    $ nosetests forgeblog.tests.functional.test_root:TestRootController.test_related_artifacts.
    ----------------------------------------------------------------------
    Ran 1 test in 3.671s
    
    OK
    
    • status: open --> code-review
     
  • Jenny Steele - 2012-03-02
    • status: code-review --> closed
     

Log in to post a comment.