Loading Profile...
Will you add the ability to show not even standard issue fields, but also custom fields?
Currently WLA`s Issues tab only displays Jira standard issue fields. It would be nice, if WLA could also display custom fields.
3
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The best answer from the company
-
Wait for it... Released! Full support for custom fields requires installation of a JIRA plugin. This plugin is free and you can use it for your other applications if you want. Documentation on the plugin is here:
http://worklogassistant.com/jira-plug...
The plugin has been tested on JIRA versions 3.10 and up.
Thanks for your patience in testing and your comments.
I’m happy... FINALLY!
The company says
this answers the question
-
Inappropriate?Yes, this is planned.
1 person says
this answers the question
-
Inappropriate?Hey Bernd,
I'm just working on this now and would appreciate if you have any thoughts to offer:
Not all issues need to have values in their custom fields. The question is: How to show this? My gut feeling for those issues is to leave those columns empty with a "-" entry, similar to how the "Pending worklog totals" column works.
Additionally, it is possible for a custom field to be multi-valued. In those cases, I am considering having a line per value, to a maximum of 3 values.
Thanks for any opinions!2 Comments Add a comment
This answers the question
-
Hi Sohail,
a "-" to indicate empty fields is perfect. But why would you restrict the display for multi-valued fields to 3 values? Could you make this a configuration feature? In any case, you should indicate that there are some omitted values. Maybe with a "..." line.
Best regards,
Bernd -
Will do. Thanks.
-
Inappropriate?Ok, I've got an initial implementation here:
http://next.worklogassistant.com
There is a huge problem: JIRA does not allow me to retrieve the names of custom fields if I am not an administrator. So you need to be an admin to use this feature currently.
I do intend to fix this in the long run, however it means that I have to create a RPC plugin for JIRA. Would this be acceptable by you?4 Comments Add a comment
This answers the question
-
One more thing: without the plugin and without administrator privileges the best I can do is list the custom field ID. So you would end up with customField_10001 as a column header. May still be useful...
-
Thank you very much! You are developing very fast!
Some thoughts:
* a column header customField_XXXX is o.k., but the real field names are even better, of course.
* for me, a Jira plugin for retrieving the custom field names would be o.k.
* there is also a problem with cascading select fields. The value of a cascading select field is not shown, but its reference id.
* for an empty description field you should maybe write also "-" (an not < no-description>).
* could you additionally retrieve the value of the component field? -
As the plugin for JIRA would require interacting with the server, something not most users would be able to do, I will first support custom fields as follows:
- For non-privileged users: customField_XXXX
- For admin users: As is now (in WLA::Next)
In the meantime, I will work on a RPC plugin for JIRA. I think it would be better overall for me to add this plugin because then I can do other things I'd like to do. Unfortunately, it will take time so I can't really specify when! One of the things that can be solved with this plugin is the cascading select field problem you mentioned as I just verified that I only get the IDs back from JIRA using their existing API. Sigh...
For the empty description, I will switch to using "-". In fact, there are a lot of places where I use <no-> and in those places I will switch to "-".
I will add the component field as well as fix versions and a bunch of other fields that are still missing!
Thanks for your feedback Bernd. -
Perfect, thank you very much Sohail.
-
Inappropriate?Hi Bernd,
I've uploaded a new WLA::Next version but I have removed the custom field functionality. The reason for this is that there are some bugs in the column display code that I do not fully comprehend yet. So I have taken a separate branch for this.
Please be sure that I will be adding at a minimum, the functionality described above minus the JIRA plugin. It just will not be immediate.
Sorry for any inconvenience.
I’m frustrated
-
-
Inappropriate?To everyone on this thread, I just thought I would give a heads up as to what is going on.
Standard JIRA's SOAP API does not expose enough information for me to do this properly. While I invented a series of hacks to make this work, I am very unhappy with these. So I am writing a JIRA RPC endpoint that the user would have to install to get support for custom fields as well as any future improvements.
The installation of the endpoint will be very simple: simply drop into the JIRA installation.
The addition of this endpoint will make many more things possible so I hope that it will be acceptable by all!
I’m happy to have a solution that will solve many problems!
-
Inappropriate?Hello everyone. Bernd, I'm sorry it has taken so long!
I've uploaded a new version of Worklog Assistant to the beta site @ http://next.worklogassistant.com/down... .
As described above, for full support of custom field names, a plugin for JIRA is required. The installation is covered here: http://next.worklogassistant.com/jira...
The plugin also adds the ability to view the remaining estimate/original estimate and time spent fields. Over time, I expect the functionality provided by this plugin to grow.
Your thoughts, comments, suggestions and critiques are much appreciated.
Thanks!
I’m happy but nervous
-
Inappropriate?Wait for it... Released! Full support for custom fields requires installation of a JIRA plugin. This plugin is free and you can use it for your other applications if you want. Documentation on the plugin is here:
http://worklogassistant.com/jira-plug...
The plugin has been tested on JIRA versions 3.10 and up.
Thanks for your patience in testing and your comments.
I’m happy... FINALLY!
The company says
this answers the question
-
Inappropriate?Bernd, I fear that your trial might have run out for Worklog Assistant. Unfortunately, I do not have your contact information so if you would like to email me directly at sohail at worklogassistant.com, then I can send you an extended trial.
Thanks for submitting this report. I hope this change makes WLA more useful for you.
EMPLOYEE
