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

[dev.icinga.com #12374] Object Downtime #80

Closed
icinga-migration opened this issue Aug 9, 2016 · 6 comments
Closed

[dev.icinga.com #12374] Object Downtime #80

icinga-migration opened this issue Aug 9, 2016 · 6 comments

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/12374

Created by bsheqa on 2016-08-09 14:29:32 +00:00

Assignee: (none)
Status: Rejected (closed on 2016-11-10 14:01:09 +00:00)
Target Version: (none)
Last Update: 2016-11-10 14:01:15 +00:00 (in Redmine)


@icinga-migration
Copy link
Author

Updated by bsheqa on 2016-09-06 07:43:35 +00:00

  • Target Version changed from 313 to v0.5.0

@icinga-migration
Copy link
Author

Updated by bsheqa on 2016-09-20 18:03:20 +00:00

  • Target Version changed from v0.5.0 to v0.6.0

@icinga-migration
Copy link
Author

Updated by bsheqa on 2016-11-09 13:17:45 +00:00

  • Status changed from New to Closed
  • Assigned to set to bsheqa
  • Done % changed from 0 to 100

@icinga-migration
Copy link
Author

Updated by bsheqa on 2016-11-10 14:01:00 +00:00

  • Status changed from Closed to New
  • Assigned to deleted bsheqa
  • Done % changed from 100 to 0

Downtimes should be created via API or command pipe. Only scheduled downtimes via puppet

@icinga-migration
Copy link
Author

Updated by bsheqa on 2016-11-10 14:01:09 +00:00

  • Status changed from New to Rejected

@icinga-migration
Copy link
Author

Updated by bsheqa on 2016-11-10 14:01:15 +00:00

  • Target Version deleted v0.6.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant