francis Atlassian Partner

There is currently no direct way to copy grids and/or construct a query which retrieves the grid data from the parent (lacking the parent:id as issue value). I raised a feature request for further trackinghttps://support.idalko.com/browse/IGRID-3247

Hi Philipp, Cloning a table grid needs support from the add-on itself. I was assuming that it could be done with a script, but we have to take into account a) the id needs to be incremented correctly b) sequence values need to be updated in case of continuous counting Also, it is currently not possible to detect that an…

The only drawback is that you need to know when the file was available in some branch. But that's fine. I will add a feature request for the 'show all'. Thanks,

Hi Kelie, There are multiple solutions available to synchronize issues from one JIRA to another JIRA. https://marketplace.atlassian.com/search?q=issue+sync If you would consider to go down the path of deploying an add-ons, please also consider our solution which has been designed for your use case: Exalate…

Hi Meysam, You did raise this issue also in our support channel - thanks. Is it ok to address it there, and then publish the outcome here ? Francis

Hi Senthilvedhan, Exalate is an issue synchronisation solution providing bidirectional synchronisation between multiple issue tracker types including JIRA, JIRA Cloud, HPALM. Send us a mail to info at exalate dot com for more information. Francis

The scheduled indexing service had been discontinued since atlassian introduced background indexing in 5.2 and improved the indexing functions in later releases. Francis

I deleted the plans which is a bit drastic.

This is correct and a know issue. We are working to resolve it asap. Francis

Jessica, There are various synchronization solutions available on the marketplace - check following query https://marketplace.atlassian.com/search?q=issue+sync 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…

Hi OliviuWe had the same problem, and I can show you how we solved it. We are also from Belgium, so give me a call whenever convenient (+32.3.808.05.89) and we'll setup a screenshare.Francis

That's an approach but it does disable the ranking in all the projects.

+1 for CMK We should be able to provide a stripped-down project setup for the occasional JIRA user who just want to raise a ticket, be able to comment, attach files/screenshots and look at the status of the issue. All the other options should be ... optional

if the schedule permission is diabled, you can't modify fix version, nor adapt due date, which are fields in use in the project.

That's an improvement request in the making :-) This JIRA instance is being used both for software development and for completely different purposes. The fact that the operation 'Rapid board' is there, requires us telling the users of the non-software development configuration to ignore it, which is not really…

Checkout Tempo Timesheets - it allows you to enforce work description https://tempoplugin.jira.com/wiki/display/TEMPO/Time+Tracking+Permissions+and+Validation

No prob - I will use the command line for now.

Hello Florian, We ended up allowing commenting, and autotransitioning the issue if a comment is provided. I guess this is no help for your case.

Bill, We really need to stop access to people profiles, and we are thinking to redirect requests to profile specific information (such as mentions and others) What would be the best way to create a comprehensive list of URL's which should be redirected ? Francis

Correct. JIRA has this 'Browse Users' global permission. This would be usefull for confluence as well.

Hi Thomas, There are different solutions on the marketplace - check following query https://marketplace.atlassian.com/search?q=issue+sync 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…

Also check out the exalate solution https://marketplace.atlassian.com/plugins/com.exalate.jiranode/server/overview Does uni and bidirectional synchronisation with one or more JIRA's Supports in addition to basic issue fields - customfields, comments (including comment edits), attachments, worklogs

<shameless plug> Have a look at the pivot gadget https://marketplace.atlassian.com/plugins/com.idalko.pivotgadget/server/overview </shameless plug>

it's a large product with a lot of features, and a lot of people working on it. We do use stories and subtasks

The answer to this question is the structure plugin using a filter and a greenhopper synchroniser. I just got of the phone with Igor from almworks. We worked out a functional configuration in less than 15 minutes. Great add-on - and great support.

This issue is resolved with JIRA 4.4.3 and Greenhopper 5.8.1 Francis

Yes - I can confirm. Disabling Greenhopper and restarting JIRA is solving the issue. Scratch head.

Well, this is the first time I've seen this behaviour.

Andrey, This could be a root cause & thanks for mentioning it. On what JIRA version did you find this issue ? Francis

Hi Nic, I'm trying to narrow down the root cause by doing a step by step. I will bring up logging also to debugging level and see if this reveals something. Francis.