Using Redmine v3.3, is it possible to have a custom calculated field based on data in two other custom fields?
e.g. Duration = Date 2 - Date 1
Specifically, I am attempting to calculate the days between two dates as a performance metric. More generally, we will be looking to eventually using other custom calculated fields (simple additions, multiplications, etc.).
It would be preferable to keep this to the "vanilla" Redmine v3.3 without additional plugins but all suggestions are of course welcome.
Not in Vanilla Redmine as of 3.3, unfortunately.
It has been requested and there was some discussion about it. The feature wasn't rejected but nobody has gotten around to building it for Redmine. You can follow the discussion/development here:
http://www.redmine.org/issues/1712
A plugin is discussed in that issue as well but - as with all plugins - a thorough check will be required if it matches your stability/security expectations.
Such feature request has been filed 11 years ago (2008-7-30), while not yet enhanced.
At the moment, you can try Computed Custom Field plugin.
Although it shows "This project is no longer maintained", it stated that it is comptatible with latest stable version of Redmine 4.0.4 (2019-06-10).
Current version: 1.0.7 (2019-01-14)
Compatible with: Redmine 4.0.x, 3.4.x, 3.3.x, 3.2.x, 3.1.x, 3.0.x, 2.6.x, 2.5.x
Related
With the new 4.0 release of Neo4J a number of deprecated features have been removed, most notably the old {parameter} reference. If you have a Neo4jRepository with a Pageable query and upgrade your Neo4j to version 4.0+ you will get the following exception:
The old parameter syntax `{param}` is no longer supported. Please use `$param` instead (line 3, column 15 (offset: 168))
"return o SKIP {sdnSkip} LIMIT {sdnLimit}"
I'm interested to know if the Spring Data Neo4J team is aware of this and working to fix the issue. And also if they plan to support both styles of parameter referencing, or only $param going forward.
The only possible workaround today is to avoid Pageableand specify SKIP and LIMIT explicitly in queries.
/Klaus
Thanks to you mentioning this, we created https://jira.spring.io/browse/DATAGRAPH-1300 and this will get fixed with the next (service) releases.
Most of the heavy lifting gets done by Neo4j Object Graph Mapper.
This includes creating queries.
There are some places in Spring Data Neo4j we have not yet updated that create queries by themself and pass those on to the OGM.
It will be part of next week‘s Spring Data Moore SR 6. Since the Spring Boot starter is part of the Spring Boot releases, you need to manually upgrade Spring Data until there is an updated starter.
We experienced strange behaviour. Especially under chrome, some items are missing. Anyone ?
Which version are you using? You should always pin the version you use, which means that once it's published, it will never change.
The code is open source, you can check yourself from the github repository and there are other more appropriate channels than Stack Overflow, IMO:
The Django weblog, where a post is published each time there is a new release.
The Django users mailing list/google group is another place where you can keep up to date.
PyPI gives you the release history.
Finally, with any open source software, don't be afraid of digging into the source code and see what has changed. Github has a great way of comparing between 2 tags, for instance for the latest 2 1.11.x relases: https://github.com/django/django/compare/1.11.16...1.11.17
There was 2 new bugfix relases published on each 2.1.x and 1.11.x branches yesterday, so if your dependencies aren't pinned, you might have auto-updated, but without further details it's hard to tell you more.
I need to generate reports in my Django project, I tried django-report-tools but it has incompatiblity with Django > 1.6 versions.
Can somebody recommend one that works with 1.8?
The reports I need are very simple, pie charts, bar charts and the like.
As https://www.djangopackages.com/grids/g/reporting/ there are some packages that are Python 3.x compatible and are released lately.
I've checked DJANGO-REPORT-BUILDER and it supports the latest.
My personal preference is to use jQuery HighCharts as Frontend and Django Rest Framework to provide Json data to the charts.
Just 4 years later :)
Check out this package
https://github.com/ra-systems/django-slick-reporting
It's a reporting engine where you can create grouped by computed reports, time series and crosstab using handful of easy lines of code.
It also comes with Charting out of the box.
Disclaimer: I'm the initial author.
Cheers mate ..
There are two main schools of thought for doing A/B (Split) Testing:
Javascript-based solutions such as Optimizely, Google Analytics Content Experiments.
Server-side solutions such as Django-AB, Splango, and django-lean. (Also, writing your own.)
My understanding is that Javascript-based solutions are spectacular for "which color button converts better," but not so great for switching out entire page layouts, and completely unworkable for trying out large functional changes such as the sequence of pages in a funnel.
That leads me towards a server-side solution. I'm not crazy about coding my own, and will do so only if there is no other option. I'm trying to add value by improving the core functionality of my site, not by creating a better split-testing framework.
The Django apps I've found for split testing are various mixtures of unmaintained, undocumented, documented incorrectly, and incompatible with Django 1.5. This surprises me, because the Django and Python communities seem to have a strong focus on good documentation. I'm also very surprised that none of the testing frameworks I've tried has been compatible with Django 1.5 -- is testing not as core a part of the philosophy in the Django/Python world as it is in Rails?
Here's what I've found:
Splango https://github.com/shimon/Splango -- Not compatible with Django 1.5 (although most compatibility bugs I found were trivial to fix). Largely un-touched since October 2010, except for a fix August 2012 which claims to make sure templates get included in the install. Since templates don't get included in the install when Splango is installed via PyPI, either the fix didn't work or didn't get submitted to PyPI. Documentation is largely accurate, but doesn't completely cover how to set up tests and get reports. It tells you how to configure the template to gather the data, but there appears to be additional steps required in the admin interface which are completely undocumented, and I'm not sure I've done them properly.
Django-lean. Original at https://bitbucket.org/akoha/django-lean has not been updated since July 2010. There is an apparently "blessed" fork at https://github.com/anandhenry2002/django-lean which has not been changed since May 2012, when it was copied over from the original. The original's documentation is incorrect in ways that make following the examples impossible. (Though you can probably muddle your way through, as I did.) The new version's documentation has formatting problems that make it difficult to read on github. (This appears to be because it's the unchanged documentation from the old project, and BitBucket syntax doesn't work on Github.) The django-lean Google Group has not had a message since July 2012.
django-mini-lean https://github.com/DanAncona/django-mini-lean -- Updated as recently as February 2013, but undocumented.
Leaner - https://bitbucket.org/brianjinwright/leaner -- Last updated July 2012, and no docs.
Django-AB -- Last updated May 2009. Is not a package, and can't be installed via PIP or PyPI. After placing the checkout in my django app folder (and renaming the folder to ab) and following the installation instructions, I get an error loading the template loader that I have not tracked down further.
So far Splango appears to be the winner, as I've actually been able to get it more-or-less working (by manually installing the templates, and then editing them to fix Django 1.5 incompatibilities).
Can anyone point me to anything I've missed?
You have missed this app : https://github.com/mixcloud/django-experiments + https://github.com/disqus/gargoyle/
And then there's waffle: http://waffle.readthedocs.org/
It's simple, updated, maintained, but not very feature rich, it doesn't have any analytics/reporting stuff integrated. But then again, google analytics or mixpanel type of service is better for this.
I first looked at Django-AB and that is almost what I wanted, but I couldn't get it to work either. After looking at django-experiments and deciding I didn't want to mess around with redis yet, I decided to roll my own. I've tried to package it up nicely and make it easy to use for the beginner. It's super basic.
https://github.com/crobertsbmw/RobertsAB
You can swap out entirely different page layouts with Google Analytics Experiments (their default experiment setup will redirect users to a different URL for each variation you have), although in general its much easier to interpret why something is more successful if you test smaller things against each other.
You are right that testing different funnels and user flows against each other using Google Analytics would require a lot of manual setup; although theoretically you could do it by swapping out different links and tracking your users with UTM campaigns.
For smaller A/B tests within the same page, I ended up using Google Analytics Experiments and writing a custom Django CMS plugin for adding a few variant options to a template, which queries the Google Analytics API and displays the correct variant using Javascript.
I'm in the middle of developing a website using Sitecore 6.5 and when my company knew that Sitecore released version 6.6 they want to use the new version instead for the project, Is there a way to convert my Items created using sitecore 6.5(webform) to sitecore 6.6(mvc) so I wont redo my work?
General content items are not affected by switching to MVC .. it would be any presentation items that you would need to update if you did make a move to MVC. As #JayS says MVC is not mandatory and you can actually mix MVC and Webforms layouts within the solution so if you wanted to convert to MVC slowly over time it would be a possibility.
Just wanted to note that there is no such thing as 'recommended releases' any more (see: http://sdn.sitecore.net/support/versioning%20policy.aspx). Lots of customers already using 6.6 in production. The upgrade from 6.5 -> 6.6 should be straightforward (but this obviously depends on the complexity of your solution).
From my understanding, you do not need to use MVC in 6.6 if you do not want to. John West has a blog about the installer and how it enables MVC. You should be able to port your existing solution up to 6.6 relatively easily, but if you wish to take advantage of MVC you'll need to alter your solution.
Note, I believe that Sitecore has not marked 6.6 as a recommended release, so you may wish to inform your company of that.
UPDATE: Thanks to Stephen for pointing out that Sitecore has discontinued using the recommended release tagging. Some of their documentation online still needs to be updated regarding this :)