We’ve launched a new Help Center!

Visit the new Documentation space for Azure DevOps, monday.com, and Jira. Or, if you require any assistance or have any questions, please visit the new Customer Support Portal for Azure DevOps, monday.com and Jira.

[Budget] Hourly Rate ($) in budgets

Gathering Feedback

Comments

5 comments

  • Avatar
    Nicole Tropper

    Hi Igor, 

    thanks for reaching out! This is an interesting request and in goes in the same direction as this existing feature request where hourly costs should be assigned on a team member level. Is this something that would work for you as well? 

    Nevertheless, I will mark this thread as 'gathering feedback' for now so we can capture interests of other users.

    Thank you and all the best, Nici 

    0
    Comment actions Permalink
  • Avatar
    Igor Abade

    Is this something that would work for you as well?

    Not quite, TBH. On one hand, rates do indeed vary based on team members. But, more frequently, they vary based on the project / role in the project - thus my suggestion to have the rates linked to "roles" (Activity Types) instead of people.

    0
    Comment actions Permalink
  • Avatar
    Nicole Tropper

    Thanks for clarifying, Igor! Noted - let's see how the community responds and hopefully we can get some input from others as well.

    Cheers, Nici 

    0
    Comment actions Permalink
  • Avatar
    Stephan Polley

    Logically, I think a hourly rate is bound to a person - at least from a cost perspective. If you want to use it for billing then I can see that it may make sense on budget level.

    Maybe there is a distinction between the cost rate and the billing rate. Billing rates could be on budget levels, but often also depending on the role. E.g. an architect gets billed differently than a Jr. Developer or and off-shore developer.

    Hourly rates for cost should not change based on project and need to be bound to a person.

     

    ...my 2 cents

    0
    Comment actions Permalink
  • Avatar
    Roman Fianta

    Thank you for your input, Stephan!

    It seems that the use cases vary, and it means for us that our solution has to be flexible enough to cover the wide variety of needs.

    All the best,
    Roman, Product Owner @ 7pace (an Appfire company)

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk