Overdue Customfield

Hmmm, installed this plugin and was able to add a custom Overdue field.  Added this to my column to my navigator, but that Overdue column remains blank.  I did reindex and had a list of issues with due dates in the navigator. 

 Is there something else I need to configure?

Note that the field just diplays something if

1. no resolution is set
2. now > duedate of issue
   I dont think you need to reindex because the field is _calculated_ and not indexed. Will test soon with the latest version if theres a bug

How can you "add the field "Due Date" as type "Date Picker" for this plugin to work," if the Due Date field already exists (as it does in all systems)? Must I add ANOTHER Due Date field?

Also -- I could have sworn there was a special mention here of how to make this work with 3.6.2. Has that been updated or removed? I only get the blank Navigator column, and I'm unsure how to change an already populated field (Due Date) to Date Picker (shouldn't it already be?).

 Please advise - this would be a nice customization.

 Thanks!     - Dawn

I change this plugin to work with estimation time field. ("estimation time" field is jira default one).

http://confluence.atlassian.com/download/attachments/162670/overduefield-0.2.jar

Hi,

I was wondering if this plugin works with subtasks, too.

Thank you,

Stefano

The plugin marks things as overdue when they are due that day.

 Like if i enter a task, mark it as due sept. 18th, the plugin will mark the task as overdue on sept 18th instead of the next day when it is actually overdue.

 So if you enter a task thats due the same day, it is overdue immediately.

 Cheers,

James

James - I see your point. To be fair, my customization (see http://jira.atlassian.com/browse/JRA-9749) assumes the same thing - that it is due at 12:01 AM that day, not close of business, or 11:59 PM. If it is due today, it is displayed in RED.

Hi,

you can change the behaviour of the plugin by simply adjusting the velocity template col-overduefield.vm .

This calculated field holds the seconds which the issue is overdue starting at 12 AM that day, as Neal pointed out. This is due to the fact that the due date timestamp only holds a date but not day time.
Edit following line

#if (!$issue.resolution && $value.intValue() > 0)
<style>
 <!--
 #issuerow${issue.id} *
 {
         color: #cc0000;
 }
  -->
</style>

to

#if (!$issue.resolution && $value.intValue() > 60*60*12)

The issue is now overdue 12 hours later.

Hope that helps

Hi Phil,

I've added ordering to your plugin, so that you can order the navigator column "Overdue" by time past.

Since it is very simple to make this change, I'll want to share it here.

You just have to use a Double for the variable duedateDiff instead of a Long.
Then you can use the jira standard Number Range Searcher to index the field.
You can even search by using this searcher.
For instance you can search all overdue by just putting 1 second into the first field of the search.
In general it is difficult to search because you need the number of seconds.

Cheers

Bettina Zucker

P.S.: 

Since I changed a little bit more than just the Long -> Double, I'll put here my code,
where (...) stands for whatever your organisation name is:

package (...).jira.plugin.overduefields; import com.atlassian.jira.issue.Issue;
import com.atlassian.jira.issue.customfields.SortableCustomField;
import com.atlassian.jira.issue.customfields.impl.CalculatedCFType;
import com.atlassian.jira.issue.customfields.impl.FieldValidationException;
import com.atlassian.jira.issue.fields.CustomField;
import org.apache.log4j.Category;
import java.sql.Timestamp;
import java.util.*;

public class OverdueField extends CalculatedCFType implements SortableCustomField{
	private static final Category log = Category.getInstance(OverdueField.class);

	public String getStringFromSingularObject(Object singularObject)
    {
        assertObjectImplementsType(Double.class, singularObject);
        log.info("getStringFromSingularObject: singularObject = " + singularObject);
        log.info("getStringFromSingularObject: string = " + singularObject.toString());
        return singularObject.toString();
    }

    public Object getSingularObjectFromString(String string) throws FieldValidationException
    {
    	if (string==null || string.equals("")) return null;
        log.info("getSingularObjectFromString: string = " + string);
        return new Double(string);
    }

	public Object getValueFromIssue(CustomField field, Issue issue) {
		long nowMillis = System.currentTimeMillis();
		long millis = 0L;
		Number duedateDiff = null;
		Timestamp nowTimestamp = new Timestamp(nowMillis);
		Timestamp duedate = issue.getDueDate();
		try {
			if (duedate!=null && issue.getResolutionObject()==null)
				millis = nowTimestamp.getTime() - duedate.getTime();
			else millis = 0L;

			if (millis>86400000) millis -= millis % 86400000;
			duedateDiff = new Double(millis / 1000L);
		} catch (Exception e) {
			log.error(e);
		}
		return duedateDiff;
	}
}

 And here is the atlassian-plugin.xml:

<atlassian-plugin key="(...).jira.plugin.overduefields" name="Overdue Fields">

	<plugin-info>
		<description>Overdue Fields Plugin</description>
		<version>2.0</version>
		<application-version min="3.4" max="3.6"/>
		<vendor name="(...)" url="http://www.(...)"/>
	</plugin-info>

	<customfield-type key="overduefield"
		name="Resolution Overdue Field"
		class="(...).jira.plugin.overduefields.OverdueField">
		<description>Field that highlights overdue Issues in Issue Navigator</description>
		<resource type="velocity" name="view" location="templates/col-overduefield.vm" />
		<resource type="velocity" name="column-view" location="templates/col-overduefield.vm" />
		<resource type="velocity" name="xml" location="templates/plugins/fields/xml/xml-basictext.vm"/>
	</customfield-type>
 	<customfield-searcher key="numberrange" name="Number range searcher"
		i18n-name-key="admin.customfield.searcher.numberrange.name"
		class="com.atlassian.jira.issue.customfields.searchers.NumberRangeSearcher">
		<description key="admin.customfield.searcher.numberrange.desc">Allow searching for a number that is in a given range</description>
		<resource type="velocity" name="search" location="templates/plugins/fields/edit-searcher/search-number-range.vm"/>
		<resource type="velocity" name="view" location="templates/plugins/fields/view-searcher/view-searcher-number-range.vm"/>
		<valid-customfield-type package="(...).jira.plugin.overduefields" key="overduefield"/>
	</customfield-searcher>
</atlassian-plugin>

Can anyone give me any pointers as to why I'm not seeing the overdue rows show up as red? I can see the date due column and can see that the entry is in the past but the entry does not show up red.

 Thanks

Hi 

Have you added the customfield to your issue navigator? Like the last column in the screenshot

Hello!
Is it possible to automatically set pre-set a date to the Due Date field, depending on the priority? That would help our business case very much.

 Thanks a lot in advance!

A project manager I am working with wanted this functionality, i.e. amount of time overdue, but also wanted the "underdue amount of time".  The term under due meant that he wanted to know in how many days an issue would be due.  To meet this requirement, I modified "\WEB-INF\classes\templates\col-overduefield.vm" as follows:

#if ($value)
    #if ($value.intValue() > 0 && !$issue.resolution)
        $!dateutils.formatDurationPretty($value.intValue())
    #end
   
    ## -2147483 seems to be the value when the "due date" is not set
    #if (($value.intValue() < 0) && (!$issue.resolution) && ($value.intValue() != -2147483))
        ## multiple by -1 to get positive number
        ## 86400 is the number of seconds in a day
        ## subtract mod 86400 to round to full day
        #set( $underdueValue = (-1*$value.intValue()) - ((-1*$value.intValue())%86400) )
       
        ## make it look nice
        $!dateutils.formatDurationPretty($underdueValue.intValue())
    #end
   
    #if ($issue)
   
        ## if late, change text color to RED
        #if (!$issue.resolution && $value.intValue() > 0)
        <style>
        <!--
            #issuerow${issue.id} *
            {
                color: #FF0000;
            }
        -->
        </style>
        #end        ## if more than 7 days late, change to BOLD
        ## 86400 is the number of seconds in a day
        #if (!$issue.resolution && $value.intValue() > (86400 * 7))
        <style>
        <!--
            #issuerow${issue.id} *
            {
                font-weight: bold;
            }
        -->
        </style>
        #end
       
        ## if due in the future, change text color to BLUE
        ## -2147483 seems to be the value when the "due date" is not set
        #if ((!$issue.resolution) && ($value.intValue() < 0) && ($value.intValue() != -2147483))
        <style>
        <!--
            #issuerow${issue.id} *
            {
                color: #0000FF;
            }
        -->
        </style>
        #end
    #end
#end

The problem is, now a bug has appeared, as can be seen in the following screenshot where there is a gap is the sorting which contains the issues which do not have a due date.  My expectation was that issues which do not have a due date would be at the bottom of the ordered list:

It just so happens that "-2147483" is the number that is returned when there is no due date, which is about 24.9 days, or between 3 weeks 3 day and 3 weeks 4 days.  Note also that Integer.MIN_VALUE = -2,147,483,648, which, when divided by 1000 as is done in OverdueField.getValueFromIssue(), results in -2147483.

So.... I am thinking that a potential cause/solution is that instead of setting the value to Integer.MIN_VALUE, it should be set to Long.MIN_VALUE. 

Now, I am not 100% sure if this would do the trick....  if the source code were provided, it would be helpful.  Please note I am using version "overduefield-0.4.jar" of this extension.

Does anybody know if this plugin is compatible with jira 3.8?

Hi Phil,

The plugin doens't work for on JIRA 3.8.  I downloaded the ver 0.4 and did everything as instructed here.  I created the new field of type "OverDue" and then also configured the issue navigator as well.  I do not see the overdue calcualtion and no high-lighting either.  Please let  me know if I am missing anything.

 Thanks,

 Mohammed

Ola,

just builded a 0.5 .jar.

overduefield-0.5-bleeding-edge.jar

tested under JIRA 3.7.4

so long
Daniel

P.S.: thx Markus for the help :]

Hey,

 I have installed this plug-in and it is great i can see all the calls are in a nice blue and all the overdue calls are red, i was wondering if there is a tweak that i can make to flag up tasks that are due that day (eg 0 minutes) to being a different colour.  Im using this software as a helpdesk and this would really aid me in being able to see what calls are due that day instead of looking down the due date field and seeing that way as im bound to miss something and have users moaning at me (like thats ever going to stop)

 Thanks in advance

Gareth Collins

Hello Phil, does this plugin work in Jira 3.12?
We tried to install it but cannot see any Custom Field types called "OverDue".

regards,
Paul