francis Atlassian Partner

Thanks for the quick turnaround

The canonical source would be Gerrit. Thanks for the replication hint.

No - it should synchronize (ie. a git pull everything something is pushed on the other repo)

That's an interesting one. SLA calculation is only done at issue level so you should have a way to calculate the customer fulfillment rate for each issue. A way to implement such calculation is adding a scripted jql function…

Will bump the version on server and see what gives.

It works perfect on scriptrunner 2.0.7 and JIRA 5.0.7 We have now a scripted field which retrieves the email address of the contact person out of the CRM, and a script listener sending email when an issue is resolved or requires feedback. It took about a couple of hours to get it up and running (and tested)

And the answer is yes. Just follow the 'Built-In Scripts Hacking Notes' https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-Built-InScriptsHackingNotes (copy the sendCustomEmail.groovy out of groovyrunner-2.1.11.jar) Thanks J, much obliged.

What a great amazing unexpected turnaround My only problem is that this instance is JIRA 5.0.7. :-/ Can I backport your change to groovyrunner 2.0.7 ?

Hi Jamie, How would you specify a 'scripted field' (of type string) in the 'to issue field' It currently returns 2013-08-20 21:53:48,062 http-8080-6 WARN admin 1313x477x1 1inm9te 127.0.0.1 /secure/CommentAssignIssue.jspa [canned.workflow.postfunctions.SendCustomEmail] Unhandled custom field type customfield_11901 If this…

Hi, Thanks for it - we tried that one but ran into a performance issue. Expect to brew some cans of coffee when you have like 4000 users, and 90 spaces. Francis

That's cool. I need a distinct list of all space administrators in all spaces, but that's a small extention. Thanks,

You might have a look at the behaviours functionality of the script runner add-on. Check out the blog on http://www.idalko.com/pages/viewpage.action?pageId=1638499 Francis

Hi Senthil, You might have a look at exalate - we provide a bridge between JIRA and HP ALM - currently in closed beta. Pricing is here http://www.exalate.com/#pricing Francis

The grid table is an ordinary sql table. Looking at the explanation - there should be no problem to integrate grid table data into eazybi. Can we setup a confcall to flesh out a procedure because my modrian skills are a bit rusty Francis

The table grid editor allows to store tabular data in a database table. This table is automatically created based on the configuration of the grid. Note that this table can be created in the database used by JIRA or any external other database. There is an extensive API (rest or java) which allows to access this data. For…

Found the reason. The status 'close' was not mapped - this is interpreted by the agile plugin as if the issue is not completed, while in fact it is.

Exalate allows to connect existing projects by uploading a csv file which maps local issues to the corresponding remote issue. image2016-12-22 5:24:55.png Check for more information Connecting existing projects. Francis

Was the add-on enabled when this happened ? Can you forward the case to support dot tge at idalko dot com ?

Hi Normann, We are encountering the same issue (on 3.5.13). When you did your analysis, did you see specific log messages pointing to OOM or other issues ? Francis

I know - but for the customer there is as the history indicates that the description has not the expected value.

Nope,Assume issue has following values* Summary = The quick brown fox* Description = lorem ipsumUser A clicks on edit and changes description in XYZUser B clicks on edit and changes summary in ABCUser A saves entryUser B saves entryThe outcome is * Summary = ABC* Description = Lorem IpsumThe history contains* User A @ time…

Bumped into this one today - customer was very concerned about data loss.

Hi Tarun, What version of HPQC are you using ? The exalate add-on allows to integrate with multiple issue trackers - including HPQC v12.02 and higher Francis

Hi Adolfo, You might use the table grid editor, and collect all the relevant statistics into a grid. By creating it on a regular base you can then find out about trends. It might be a good use case to further develop. Francis

We are using the JIRA features of confluence to create tasks (in JIRA). The JIRA Issues macro is used to list all the unresolved. Not really lightweight tasks anymore, but good enough.

Hi Guilherme, it is what Bill says, this feature is not available. I found some suggestion to query the database directly using the SQL plugin, but that is paying option. We will use an alternative approach for now.

thank you - this works.

We found following solution a) Using workflow properties, set the issue non editable b) add a transition with a transition screen containing the label field. Ensure that the transition workflow property allows to edit the issue. When a user wants to edit the label field s/he needs to use the transition itself.

Would there be a way to copy it ourselves using some scripting ? Are there any api's available ?

Hi Nic / Christian, (I'm from Exalate) We are involved in a 3 way JIRA mirror project pilot at the moment. Just send a mail to support@exalate.com if you're interested in the outcome of the pilot, or book a meeting on https://exalate-demo.youcanbook.me to further discuss your scope and next steps. Francis