Project

General

Profile

Actions

Patch #26359

closed

User linking by id ("user:74")

Added by Andrey Lobanov (RedSoft) over 7 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Text formatting
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

I think this feature won't hurt.
So now you can type:

user:74

and
user:woblavobla


Files

User_linking_by_id.patch (661 Bytes) User_linking_by_id.patch Andrey Lobanov (RedSoft), 2017-07-05 15:36
Actions #1

Updated by Mischa The Evil over 7 years ago

  • Category set to Text formatting
  • Status changed from New to Needs feedback
I don't get it. What does your patch add in contrast to what is already supported? As of Redmine 3.4.0, user links in the following formats are supported:
  • user#userid (eg. user#1)
  • user:login (eg. user:admin)
  • @login (eg. @admin)
For the rationale behind the supported syntax, see #4179. Basically, it comes down to this:
  • Redmine links with a pound sign behind the object take a numerical value
  • Redmine links with a colon behind the object take a textual value

Can you please elaborate on the purpose of and rationale behind your patch?

Actions #2

Updated by Andrey Lobanov (RedSoft) over 7 years ago

Mischa The Evil wrote:

I don't get it. What does your patch add in contrast to what is already supported? As of Redmine 3.4.0, user links in the following formats are supported:
  • user#userid (eg. user#1)
  • user:login (eg. user:admin)
  • @login (eg. @admin)
For the rationale behind the supported syntax, see #4179. Basically, it comes down to this:
  • Redmine links with a pound sign behind the object take a numerical value
  • Redmine links with a colon behind the object take a textual value

Can you please elaborate on the purpose of and rationale behind your patch?

I'm sorry my local trunk was at 3.3.0, so this feature wasn't implemented.

Actions #3

Updated by Mischa The Evil over 7 years ago

  • Status changed from Needs feedback to Closed

I'm sorry [...]

Not a problem. I'll close this issue accordingly.

[...] my local trunk was at 3.3.0, so this feature wasn't implemented.

OT: still, your patch won't apply to 3.3.0 either...

Actions

Also available in: Atom PDF