Comments
-
The pivot gadget has been developed to support our Table Grid Editor customers who are looking for an easy way to report on the values stored in the tables. Given that the table grid editor is only server side, we focused on that environment first. Porting the gadget to the cloud is certainly on our roadmap, but the…
-
Hi, Someone pointed me to this question (we are developping the table grid editor) Service desk is currently not supporting complex custom fields like the table grid editor. We asked for suggestions to integrate it on SD through the JSD JIRA and also by talking to the SD developers during Summit. I guess it is in the…
-
Well, that's now the case. Still they can access the rapid board which is obviously completely empty. I'm wondering if that access can be hidden.
-
Hello Mike, There are different solutions on the marketplace - check following query https://marketplace.atlassian.com/search?query=issue%20sync We are the team behind Exalate (which is one of these solutions) https://marketplace.atlassian.com/plugins/com.exalate.jiranode/server/overview It fully covers your use case, and…
-
(sorry that I didn't followup earlier - JIRA is much easier to track issues than answers) Can you check following stackoverflow document http://stackoverflow.com/questions/12155648/how-to-fetch-text-column-value-from-postgresql Locate the last answer ... select convert_from(loread(lo_open(comments2::int, x'40000'::int),…
-
Textarea columns are clobs allowing to store huge comments. This clobs are implemented differently depending on the database system. What database are you using ?
-
Hi Guilherme, Have a look at this faq https://wiki.idalko.com/display/TGPD/How+is+the+grid+table+identifier+calculated All tge based data is stored in a table which is managed by the add-on. The number in the CF is the number of rows in the grid for that particular issue. Let me know if this helps, Francis
-
Hi Kate, We are planning to upgrade, and we are extensively using script runner, so your post is really interesting. What is debug logging on com onresolve spitting out ? (Admin -> Logging & Profiling -> add class ...) Francis
-
Consider using a scripted field where the logic collects all the custom field data and formats the view as a table. It might be straightforward, but you'll have to tweak a bit as I'm not sure what renderer is being used to show the content of the scripted field
-
Thanks Paulo, that's a workaround, but not really acceptable for the users. I followed your suggestion and created a story request https://jira.atlassian.com/browse/GHS-6569 .
-
(thanks Nic) Hi Bonita, I'm from Exalate - we organise a small workshop to get your synchronisation in place. Feel free to book a meeting at https://exalate-demo.youcanbook.me at your convenience. Francis
-
Cool - thanks for the nice words. A review on the marketplace is always welcome https://marketplace.atlassian.com/plugins/com.idalko.jira.plugins.igrid/server/reviews F.
-
OK - it is a good idea. We do have col.xyz.hidemode which specifies when the column should be showed. We can add the 'empty' option. Also - if you have screen estate issues - check the gd.fitcolumns property which might be a help.
-
Hello Peter, You can hide columns, but not dynamically. It is either visible or hidden. Can you elaborate on the use case ? Francis
-
Euroxid, I'm bumping also into this one yesterday. I installed JIRA service desk, and since then no joy anymore. Removing caches, indexes, bundled_plugins, osgi_plugins and so on didn't help. So I cleared the database, brought up JIRA, imported an xml backup from the day before yesterday, and JIRA is humming happy again.…
-
That's a cool approach, not requiring to access JIRA 'behind the scenes' Certainly a candidate for a build-in script (IMO)
-
We are currently using a query on the database, but I'm wondering if there is another approach. The query is something like select workflownamefrom jira.jiraworkflowswhere descriptor like '%iamhuy%'
-
FYI col.xyz.formatNumber has been released in 1.13
-
Hi Stephan, We are currently working on the calculated column feature. You will be able to add a formula to each column of type string, integer or number. For example: col.linetotal.type=number col.linetotal.formula = {quantity} * {price} * {discount} The obvious next step is of course a number formatting capability…
-
There is a workaround which requires some additional configuration, but which might be usefull going forward. The table grid editor supports to load data using a dyamic query https://wiki.idalko.com/display/TGPD/gd.query This query can retrieve its data from a driving table…
-
The script calls an utility function - returning a list of issues. (Not sure what the new answers will do with the next piece of code)When we run another query like 'project = MRM and resolution is empty', the query runs fine.{code}class SearchUtil { private static Logger log = Logger.getLogger(SearchUtil.class); private…
-
Scott, sorry to say but my earlier proposed workaround is not an option as all internal comments are visible to customers when they get access to the JIRA view of the issue. The only workaround would be to track these public issues in another - non service desk related - project.
-
When you allow customers access to JIRA issues (by including them in the jira-users group), they will be able to see both internal as external comments ...
-
Oops - glad that it helped and kudos to Andrey.
-
Hi Jon, I'm not sure if you want to continue the discussion here or on our support site, but in any case - could you share your grid configuration ? Thanks, Francis
-
Good idea - we will give it a try - thanks
-
I was not trying to put it in an URL, but in a comment about what the target domain name should look like. Thanks - both answers look equally good.
-
Did you try jdigest ? https://plugins.atlassian.com/plugin/details/19656 It's a commercial plugin but it allows to summarize notifications.
-
This is a production system - so I can't experiment. I removed the commentvalidator from the workflow, which obviously resolved the symptom.Will try to reproduce on test system.
-
Got the same thing but cycling the addon is not resolving the problem, which is happening since we installed the service desk add-onThis stack trace is raised when you have a 'commentvalidator' script in your workflow transition.The full stack trace is http://pastebin.com/B4Sj2Ak1