[#JRA-5223] Issue key regex is broken with punctuation

JIRA

Issue key regex is broken with punctuation

Created: 13/Nov/04 06:30 PM Updated: 30/Jul/06 07:35 PM

Component/s:

Web interface

Affects Version/s:

3.0.2

Fix Version/s:

3.1

Time Tracking:

Not Specified

File Attachments:

JiraKeyUtils.class (6 kB)

Issue Links:

Duplicate

This issue is duplicated by:

~~SVN-16~~ Issues surrounded by [] don't get indexed

~~SVN-6~~ Indexer doesn't recognize issues in log messages surrounded by []s

Reference

This issue is related to:

~~PERF-27~~ Indexer doesn't find all of our Jira issue numbers embedded in comments

Participants:	Brian Lalor, Jeff Turner [Atlassian], Mike Cannon-Brookes [Atlassian] and Scott Farquhar [Atlassian]
Since last comment:	3 years, 41 weeks, 4 days ago
Resolution Date:	13/Nov/04 06:30 PM
Labels:

Description

« Hide

As reported by users of the Perforce plugin, JiraKeyUtils isn't correctly identifying issue keys when they're surrounded by [] - ie ~~JRA-107~~.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Mike Cannon-Brookes [Atlassian] added a comment - 13/Nov/04 06:30 PM

I've fixed this in CVS, needs to be ported to the bug fix branch.

[ Permlink | « Hide ]

Mike Cannon-Brookes [Atlassian] added a comment - 13/Nov/04 06:41 PM

If you drop this class into WEB-INF/classes/com/atlassian/jira/util it should patch the problem until the next JIRA release.

[ Permlink | « Hide ]

Brian Lalor added a comment - 19/Nov/04 06:56 AM

Is it acceptible to put this .class file in edit-webapp/WEB-INF/classes/com/atlassian/jira/util ?

[ Permlink | « Hide ]

Scott Farquhar [Atlassian] added a comment - 21/Nov/04 04:59 PM

Brian,

That is fine, provided that you remember to build the war file afterwards.

Cheers,
Scott

[ Permlink | « Hide ]

Jeff Turner [Atlassian] added a comment - 20/Dec/04 11:02 PM

D'oh, we didn't port this fix back to 3.0.3

[ Permlink | « Hide ]

Jeff Turner [Atlassian] added a comment - 20/Dec/04 11:02 PM

This also causes the CVS log parser to miss issues containing strings like '[FOO-123] Fixed'.