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 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
From what I can see there are two current problems:
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.
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)
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: https://answers.atlassian.com/questions/115221/set-worklog-by-script
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot