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

Carlos Reyes

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

— THEN

The Original Estimate of the issue will be set to 5m.
Edit | Move Up | Move Down | Delete

— THEN

Creates the issue originally.

— THEN

The Time Spent of the issue will be set to 5m.
Edit | Move Up | Move Down | Delete

— THEN

The Resolution of the issue will be set to 1.
Edit | Move Up | Move Down | Delete

— THEN

Set issue status to the linked status of the destination workflow step.

— THEN

Stores updates to an issue (no change history is created).

— THEN

Re-index an issue to keep indexes in sync with the database.

— THEN

Fire a Issue Created event that can be processed by the listeners.
Edit

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

Carlos

Dave C

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.