#5730 All comments are lost after moving a ticket

v1.0.0
closed
nobody
42cc (432)
General
Dave Brondsema
2015-08-20
2013-02-01
Igor Bondarenko
No

Seems like this is related to latest changes to 'ticket move' feature in [#5708] and [#5691]

Related

Tickets: #5666
Tickets: #5691
Tickets: #5708
Tickets: #5727
Tickets: #5730

Discussion

  • Igor Bondarenko - 2013-02-01
    • status: open --> in-progress
     

  • Igor Bondarenko - 2013-02-01

    Created #256: [#5730] All comments are lost after moving a ticket (2cp)

     

    Related

    Tickets: #5730

  • Dave Brondsema

    Dave Brondsema - 2013-02-01
    • labels: --> 42cc
    • milestone: limbo --> forge-backlog
     

  • Igor Bondarenko - 2013-02-05

    Closed #265. allura:je/42cc_5730.

    It fixed bugs with comments, but I've got one more concern. What is a proper way to handle ArtifactReferences when moving a ticket?

    Would it be ok to delete all refs and backrefs to the ticket that was moved and create a new ArtifactReference for it? Or it needs more sophisticated logic to make all links to the ticket refer a new ticket location (don't sure if it's possible)?

     

  • Igor Bondarenko - 2013-02-05
    • status: in-progress --> code-review
     

  • Igor Bondarenko - 2013-02-05

    Also it contains changes from [#5666] with corresponding fixes.

     

    Related

    Tickets: #5666

  • Dave Brondsema

    Dave Brondsema - 2013-02-05
    • status: code-review --> closed
    • qa: Dave Brondsema
    • milestone: forge-backlog --> forge-feb-08
     

  • Dave Brondsema

    Dave Brondsema - 2013-02-05

    Looks like current behavior is that backrefs to another artifact still work fine. A forward ref will still exist (and work) but the link within the markdown doesn't work. After updating that referring artifact and it gets reprocessed, then the forward ref is removed too.

    I'm okay with that. Seems pretty good and I don't think we could get much better without putting a lot of work into it.

     

Log in to post a comment.