Post function Time Spent not working in a simple workflow Jira 4.4

G'Day Jira Gurus,

I have a very simple workflow

Create (status) ------ Create Transition ----> Closed (Status)

I am using post functions in the create transition

All Validators (1) Post Functions (9)

Add a new post function to the unconditional result of the transition.

The Assignee of the issue will be set to dbond.
Edit | Move Down | Delete
The Original Estimate of the issue will be set to 5m.
Edit | Move Up | Move Down | Delete
Creates the issue originally.
The Time Spent of the issue will be set to 5m.
Edit | Move Up | Move Down | Delete
The Resolution of the issue will be set to 1.
Edit | Move Up | Move Down | Delete
Set issue status to the linked status of the destination workflow step.
Stores updates to an issue (no change history is created).
Re-index an issue to keep indexes in sync with the database.
Fire a Issue Created event that can be processed by the listeners.

The Post Function Time Spent is not working. Every thing else works fine

Any ideas why the Post Function Time Spent is not working?

I appreciate your assistance


1 answer

1 accepted

0 votes
Accepted answer
David Currie Atlassian Team Mar 03, 2013

From what I can see there are two current problems:

  1. Time logged does not seem to be working - I believe this is a bug and have raised it under JRA-31929. Please watch that issue for future updates from the devs and PMs.
  2. To set a resolution on the issue during Create Issue, as in our Special Cases you'll need to configure it in a particular way. Please check out those docs as they instruct how to do so.

However, this is a bit of an edge use case and not exactly how we expect JIRA to be used. Is there any particular reason for creating issues this way? If we could get a better understanding of what the context is for this, we may be able to suggest some other options. Specifically, what's the user trying to do with this behaviour? It would make sense to log work against one issue rather than creating an issue for every 5 minute block. For example, say you need to track administrative tasks for a month, you could have one issue open for that month and log each section of work in there. When that month is over, you can create a new one. I suggest keeping it monthly as excessive log tracking in one single issue is known to cause problems.

Thanks David,

The resolution is working fine and the documentation was instrumental to achieve that. Basically the problem I have is a bug as reported in JIRA-31929

I have a client who wants to create issues by email only for statistical pourposes.

She wants that the issues to be created closed with specific assignee assigned and time spent set to 5 minutes. (It does not mean that an issue will be created every 5 minutes but when she actually works on one and email it to Jira then the time spent should be around 5 minutes)

Anyway, she still want to go ahead but It would be useful to have this "Time Spent" fixed (I am watching issue JRA-31929)



David Currie Atlassian Team Mar 03, 2013

You're welcome! Glad to hear that helped you with the resolution. I suspect that the bug may not actually be fixed as setting that time logged field can break GreenHopper time calculations.

I'd suggest looking at an alternative solution as well, for example you could write a script using Script Runner that would log work - there's another example question on this topic that may assist:

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,088 views 4 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you