Greenhopper "Time Remaining" incorrect.

[willem odendaal]

I've seen similar questions to this one, but none answer my question.

When I look at the Greenhopper Planning board, on the right hand side under the current Version it states that only 6h 11m of time has been spent out of 418 hours.

However, when I look left to the tasks, I can clearly see that about 80 hours have been logged when adding up the Time Spent displayed on each card.

Where does Greenhopper get its incorrect time spent calculation from?

UPDATE (Monday 07 May):

When I look at this page now the time spent only shows the hours I logged this morning, completely ignoring the previous time spent as per the previous screenshot. See new screenshot below.

Am I wrong in assuming there is something seriously buggy with how Greenhopper calculates the time spent?

PS: time version start/end date is from 20 March to 25 May.

[Ashley Hudson]

Heya @Olga Videc ,

For limiting request types based on groups, this currently doesn't exist as of yet! From my understanding the method I would suggest would be to create two separate jira projects and limit the access based on their customer permissions. In JSM, you can control project access by using "Customers Permissions" to essentially prevent users from seeing the project and its associated requests submission UI via the portal.

So although it doesn't exist as of yet, hopefully this workaround is good! You can also create automation rules which automatically populate tickets and create issue links between the newly requested tickets so you can track in one single project rather than the two projects (if you want to have the projects "centralised")? (On the back of that, you'd want to create automation rules which creates a comment on the duped issues ticket & updates the status )

I hope this helps you and please let me know if you have any other questions :)

Kind Regards,

Ashley Hudson