Apache Allura™

Forge software for hosting software projects

Brought to you by: alexluberg, brondsem, deshani, dill0wn, and 10 others

#5691 Incorrect tickets instance in notification mail

Milestone: v1.0.0

Status: closed

Owner: nobody

Labels: support (446) p3 (267) 42cc (432)

Component: General

Reviewer: nobody

Updated: 2015-08-20

Created: 2013-01-25

Creator: Chris Tsai

Private: No

I've been seeing quite frequent incorrect ticket instance references on notification mails.

I have moved tickets between these two tickets instances, though the tickets where I'm getting incorrect references for were not themselves moved.

Headers from an incorrect email, I can grab at least a dozen more examples if necessary.

To: "[forge:feature-requests] " 2500@site-support.forge.p.re.sf.net
From: "Chris Tsai" ctsai@users.sf.net
Reply-To: "[forge:feature-requests] " 2500@site-support.forge.p.re.sf.net
Subject: [forge:feature-requests] #2500 HTTP 500 error on hg push
Message-ID: /p/forge/site-support/2500/114d1094c560234da86d442b7cf04ddcfa7bc92d.feature-requests@forge.p.sourceforge.net
Date: Fri, 25 Jan 2013 20:55:26 +0000

Related

Git: 578d5c2f6d19cd7f9250eef7
Tickets: ~~#5691~~
Tickets: ~~#5727~~
Tickets: ~~#5730~~
Tickets: ~~#5903~~

Discussion

Dave Brondsema - 2013-01-29

labels: support, p3 --> support, p3, 42cc

milestone: limbo --> forge-backlog
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Igor Bondarenko - 2013-01-30

Created #263: [#5691] Incorrect tickets instance in notification mail (2cp)

Related

Tickets: ~~#5691~~

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Igor Bondarenko - 2013-01-30

status: open --> in-progress
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Igor Bondarenko - 2013-01-30

Could you show an example of incorrect reference that you have? What location it points to and what should it be?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Chris Tsai - 2013-01-30

All the examples I have currently are like the headers I provided. They reference "[forge:feature-requests]", when it should be "[forge:site-status]"

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Igor Bondarenko - 2013-01-31

status: in-progress --> code-review
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Igor Bondarenko - 2013-01-31

I was able to reproduce it, following this steps:

move any ticket from tracker1 to tracker2

comment any other ticket in tracker1

you will get references to tracker2 (should be tracker1) in comment notification

It is the same bug as in [#5708]. So I've added a test for this scenario to fixes from allura:je/42cc_5708.

All changes in allura:je/42cc_5691.

Also, see my comment: https://sourceforge.net/p/allura/tickets/5708/#4223
I have been thinking maybe we should add some kind of paster command that would fix messed up discussion instances for trackers.

Related

Tickets: ~~#5708~~
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2013-01-31

Yes, we should fix up the existing issues. Can you create an allura ticket for it and put it in your queue?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2013-01-31

status: code-review --> closed

milestone: forge-backlog --> forge-feb-08
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Igor Bondarenko - 2013-02-01

Created [#5727] for that.

Related

Tickets: ~~#5727~~

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.