Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors: Remaining estimate must not be empty, Work attribute 'Activity type' is required #30

Open
i-grou opened this issue Aug 17, 2020 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@i-grou
Copy link

i-grou commented Aug 17, 2020

Can't log the time because some additional fields are required, but can't find the way to add them to the command, hence I'm getting an error:

Failure. Reason: Request failed with status code 400. Errors: Remaining estimate must not be empty, Work attribute 'Activity type' (_Developmentactivities_) is required

Is there a chance that parameters mentioned above would be supported? Also it would be great to calculate remaining estimate automatically when logging time.

@szymonkozak szymonkozak added the bug Something isn't working label Aug 17, 2020
@szymonkozak
Copy link
Owner

szymonkozak commented Aug 17, 2020

Hi,

as long as tempomat is connected only to the Tempo API and isn't connected to the Jira API we cannot calculate remaining estimate parameter, because current estimate value it is not available anywhere in the Tempo API (See https://tempo-io.github.io/tempo-api-docs/)

I can add a new option to log command to support this parameter. For example --remaining-estimate (with -r alias). But I am not sure what should we do if this option is not present. We can just do "nothing" (this is the easiest way). Also we could set it by default to 0h (but I don't know if that's a good idea, because it would override recalculated value for some configurations) or we could detect Remaining estimate must not be empty error and send request again with 0h value, but then logging would take longer. What do you think about this?

As regards custom work attributes, this seems to be more challenging. I personally don't use any custom attributes, so I have to check it out and I let you know what can I do with this.

@i-grou
Copy link
Author

i-grou commented Aug 17, 2020

Thanks @szymonkozak,
the --remaining-estimate / -r looks fine. Maybe we could have some config for that instead of trying to detect errors, e.g. user would be able to edit config file if needed to add remaining estimate parameter.
Maybe config file could be also used to add custom attributes list.
BTW config file may be useful to provide default values for custom attributes, but not sure if it would be useful :)

@szymonkozak
Copy link
Owner

Remaining estimate can be used in v1.2.0-beta.0 version. Custom attributes will be added when a new config format is ready.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants