Redmine

Nice, Thanks.

On pages with wiki fields, formatting eats out all line breaks. Is it the expected behavior?

Thanks for your feedback, Alex.

I managed to reproduce the behaviour you are describing. I confirm that it is not an expected behaviour, and also that is is not convenient.
I will correct it in next release.

A workaround, is to put 2 line breaks.

Thanks for this nice plugin. I use it often. I’m not sure if this an issue with this plugin. When sending out a notification email the server treats links created with issue_fields differently than just using the regular "#issue_number" format. For example, links created with each method look like the following:

issue_fields link: /issues/1313
regular link: base_uri/path/issues/1313

When a user clicks on the link in a notification email created with issue_fields, the link is broken. The links that use the regular method don't break.

Mauricio Cordero wrote:

Thanks for this nice plugin. I use it often. I’m not sure if this an issue with this plugin. When sending out a notification email the server treats links created with issue_fields differently than just using the regular "#issue_number" format. For example, links created with each method look like the following:

[...]

When a user clicks on the link in a notification email created with issue_fields, the link is broken. The links that use the regular method don't break.

I am able to reproduce that behavior.
In my plugin, I use internal Redmine's functions to manage hyper-links. Redmine use to work with relative links, and it manages to add the correct URI.
In the particular context of mail notification, I don't know at the moment, why the links keep relative.

This is a nice improvment for next release.

Thanks for this nice plugin. I find it very useful for creating release notes.

I am using Redmine 3.0.4, and have run into a small problem.

If I use the plugin without any option, it works fine. For example

{{issue_fields(7397,status,subject)}} 

But if I use any of the option, I get an error. For example, if I use:

{{issue_fields(7397,-C,-p,status,subject)}}

I get the following error:

Error executing the issue_fields macro (Couldn't find IssueCustomField with 'id'=all [WHERE `custom_fields`.`type` IN ('IssueCustomField')])

Please advice.

Hello

thank you for your feedback.

I have updated, corrected and improved my plugin since the initial revision.
It is tested on versions 2.6 and 3.1 of Redmine.
I have to post the last release, to share those improvements.

In coming days.

Thanks for your prompt reply.

Another point that I noted is, the issue number appears the same independent of the status.

Compared to this, when I see the issue list in my road map, the closed issues appear with strike through font (see attached screenshot)

Hello Vikram

I have posted the new release of the plugin, version 0.4.7
This version brings corrections and new features.

An important evolution deals with options. I try to make the new release compatible with old ones, but I recommend to use the new syntax.

Another great improvement, is the possibility to give a list of issues, instead of a single issue. This way, with a single call to the macro, it is now possible to display several issues.

The new release has been successfully tested on Redmine version 2.6 and 3.1.

@Stéphane Briand SeaSideTech
Could it support redmine 3.3.X? Thanks.

Steven Wong wrote:

@Stéphane Briand SeaSideTech
Could it support redmine 3.3.X? Thanks.

Hello Steven

Not tested on redmine 3.3.x, so I cannot state if it will work or not.
Nevertheless, you can test it safely, because this plugin has not impact on the SQL DataBase.
There is not risk of corruption.

In the worst case, you will get error message.

Let me know it you test it successfully on redmine 3.3.x

Thanks

Stéphane

Thanks Stéphane for super quick turn around.

I will try it out.

Regards,
Vikram

Hello Stéphane,

The new version is working fine with 3.0.4.

The new syntax is cool.

Just loud thinking (I know its not part of your plug-in scope), but can this feature not go in as part of Redmine core? For example, the way we have facility to specify a text for a URL/link, may be we can have similar syntax for issue listing:

#123:"status,subject" 

Thanks.

Vikram

Vikram Lele wrote:

Hello Stéphane,

The new version is working fine with 3.0.4.

The new syntax is cool.

Just loud thinking (I know its not part of your plug-in scope), but can this feature not go in as part of Redmine core? For example, the way we have facility to specify a text for a URL/link, may be we can have similar syntax for issue listing:

[...]

Thanks.

Vikram

Thank you for your feedback.

For features that deals with redmine core, I cannot help (as I am not involved in core developpement).
I don't understand what you mean with the URL/Link.

In wiki, as you already know, for specifying a clickable URL/link on a text, we use the following syntax:

here is a link to "my website":http://www.promorphosis.com

which appears as:

here is a link to my website

On the same lines, it would be great if the Redmine core permitted specifying the information to be displayed with the issue number using a syntax that is more intuitive than the standard plug-in like syntax.

I know this is something that Redmine core team has to decide. I just wanted to log the idea (may be I should post it as a feature request in redmine project).

It seems that using the Wiki Issue Fields methods allows for wiki content to reference private issue elements when they should not - like when the wiki reference itself is in another project. Private issues should remain private and not reference-able from outside the bounds of that privacy.

Any plans to ensure privacy?

The utility of this plugin looks great - but the privacy thing keeps us from using this plugin in our instance.

Hello Tom Filiaggi

I made some test to check that privacy is respected. I don't find problem with the last version of the plugin (i.e. 0.5.1).
Could you test this version, a give me more details (screen shots, dumps...) of the problems you see?

Kind regards

Stéphane

Hmmm - another person on my team tested this and brought it to my attention, but as I just tested it myself, it does appear to be behaving as expected. Private issues are producing the error condition for users that should not have access to the private issues. It looks like there is no action here.

Thanks for spending the time to test this. If it turns out that there truly is an issue and I just misunderstood it, I will post an update here.

OK - clarification regarding the "privacy" issue:

The actual concern was the content of the error message (not access of private content) when access is attempted for content that the user does not have authorized access. The error presented is an "undefined method" error. It would be "nicer/cleaner" if the error message stated something related to access permissions.

But this is quite minor, as the error message already attributes to the "issue_fields macro", which should be descriptive enough.

Yes, I agree that a specific error message is better and more clean than a generic system error message.

I will improve that as soon as possible.

Hello Stéphane,

Thanks for the nice plugin. I am using wiki_issue_fields_0.5.1.zip and Bitnami Redmine 3.3.2-2. Issue field "assigned_to" is producing no output -- issues are definitely assigned to a developer, but something like {{issue_fields(222,-l,assigned_to)}} returns nothing. Other fields like "subject" and "due_date" work just fine and return proper information. Have you observed such behavior? Can you suggest a fix or workaround?

Many thanks,
Cristiano

Cristiano Krug wrote:

Hello Stéphane,

Thanks for the nice plugin. I am using wiki_issue_fields_0.5.1.zip and Bitnami Redmine 3.3.2-2. Issue field "assigned_to" is producing no output -- issues are definitely assigned to a developer, but something like {{issue_fields(222,-l,assigned_to)}} returns nothing. Other fields like "subject" and "due_date" work just fine and return proper information. Have you observed such behavior? Can you suggest a fix or workaround?

Many thanks,
Cristiano

Hello

you are right, there was a mistake in my plugin.
I have solved it.

New version published of my plugin, that include this correction : 0.5.2

Stéphane Briand SeaSideTech wrote:

Hello

you are right, there was a mistake in my plugin.
I have solved it.

New version published of my plugin, that include this correction : 0.5.2

Ok, it is working great now! Thanks!

Hi,

thank you for developing very useful plugin.
Recently we found out that </br> in a long text box can not be displayed properly in Wiki page.
Could you fix it?

We are using Redmine 2.6.9.stable and wiki_issue_fields 0.4.7.

Awaiting your prompt reply.

Thanks.

to Eri Onoda

Hello

Is it possible for you to upgrade the plugin with the latest version 0.5.2
It brings some great improvements, and solves some issues (like line break in descriptions)

Stéphane