Comments
-
I've seen it and installed it immediately on our JIRA.It is great, including the configuration capability. very cool.
-
Yes - that would be a start - for instance red border when it is a comment for all users, green border when it is restricted.In a later phase one can imagine that each level has a different border color / background / image configurable through the admin
-
Check out https://jira.atlassian.com/browse/JSD-270 There are 210 votes and a huge number of comments on this one. Francis
-
Using basic authentication allows you to create remote links but only in the context of the user which is used to authenticate the application link, which is not what we want. Ondemand is therefore no option anymore, and Atlassian is phasing out enterprise hosting, so we will have to look elsewhere. grmbl
-
The grid configuration validation check will test the gd.query sql by adding 'limit 1' to the query string and run it. Could you send this case to support dot tge at idalko dot com, so that we can further track the issue with our JIRA ? Thanks, Francis
-
Hi Max, When creating an issue, the issue id is still tbd. Therefore you can't use it at that moment. Could you try to reload the grid (using the reload button on the grid toolbar) once that the issue is created and see what gives Francis
-
Hello Anthony, I missed your comment - sorry about that. How relevant is it to further the discussion ? Francis
-
gd.query.ds is used to specify on what data source the query should run.https://wiki.idalko.com/x/64Lggd.query is used to specify the query itselfhttps://wiki.idalko.com/x/zoLgSo your grid configuration should look likegd.query.ds = jiragd.query = select cfo.customvalue ...(When pretty formatting a query make sure you use…
-
Hi Anthony - given the limited formatting capabilities of a comment, I'm adding a reply to your last remark here ... This can be done by configuring gd.query to retrieve the selected values. An example query (here specific for mysql) would look like following snippet - with 10070 the customfield id gd.query = SELECT…
-
Hello Anthony, Check out the inline parameters page https://wiki.idalko.com/display/TGPD/inline+parameters+method You can write a query like ...gd.query = select a, b, c, d from myTable where e = {currentuser:id}... ...col.mylist.type = listcol.mylist.query = select a, b, c from myTable where e = {customfield:10401}...…
-
Found the answer in the documentation - these 'to be created pages' are called 'undefined pages' and managing them is dead simple https://confluence.atlassian.com/display/DOC/Managing+Undefined+Pages?src=search
-
Hi Jim, I raised an issue on our JIRA to further track down this request https://support.idalko.com/browse/IGRID-3043 Francis
-
Hello Ilva - the root cause for this problem can be completely different than the one from Zeynep. Could you raise a support ticket on our jira by sending an email to support.tge@idalko.com ?
-
Got it - I replied.
-
Hi Zeynep, I have seen your message on slideshare - but for some reason email gods are not with us. Could you raise an issue on our issue tracker directly at https://support.idalko.com/servicedesk/customer/portal/5 Thanks, Francis
-
That's bad news. I tried it (on 5.2.2) and it did convert 2400+ users correctly, but this was on a test machine. I'm wondering what would happen when we do the production upgrade.
-
Indeed, 3.13 is a challenge. It might depend on the use case and what information needs to be exchanged. Exalate can support it, but it would require the development of a new connector.
-
I agree with Nic. The best integration of Service Desk with JIRA server is when installed on the same JIRA. Still - In some cases you want to separate out both instances (ie for security reasons and so on). If you would consider such approach, there are a number of commercial add-ons which provide the capability to…
-
There are different solutions on the marketplace - check following query https://marketplace.atlassian.com/search?q=issue+synchronisation 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 we are…
-
We resolved in another way (not with FormNG). Now that you bring up the contacts - I'm wondering if Adaptavist is tracking plugin specific questions on AAC ? AAC is much more efficient than any direct support channel as other people would benefit from their answers.
-
Yes - it is set to rendered
-
Hello Eldon, There are different solutions on the marketplace - check following query https://marketplace.atlassian.com/search?q=issue+synchronisation 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…
-
And Exalate is another serious offer * Supports Cloud to Cloud synchronisation (next to Server/Cloud and Server/Server) * Doesn't require a standalone server More information can be found at * Marketplace listing * Documentation site Francis
-
Is there a way to have the gantt-chart plugin show epics and their contained stories ?
-
Hello Soumia - how did you restore the data on the new JIRA server ? Francis
-
We are using sonar to do this type of static code analysis. There are great plugins to integrate sonar with the atlassian tools. Check here https://marketplace.atlassian.com/plugins/com.avainit.bamboo.bamboo_sonar
-
It is pretty straightforward to specify what information can be sent over using exalate. It has the concept of a data filter where you can detail out what labels can be sent. This data filter is actually a groovy script which is used to setup the message that will be sent over to 'the other side' This groovy script can…
-
I bumped also into this one. The reason is that there is some incompatibility between Chrome/Firefox and the latest version of java (7u11). There is a lot of discussions on this topic in various forums. I solved it by downgrading to java6u38 - (32bit for Chrome), which can be found…
-
No - not yet.
-
You can use standard JIRA functionality for this type of reports. For instance * The average age report https://confluence.atlassian.com/display/JIRA/Average+Age+Report * The average age gadget https://confluence.atlassian.com/display/JIRA/Adding+the+Average+Age+Gadget Hope this helps, Francis