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 #12020] Decide whether to use strings or constants for state/type filters in the documentation #4311

Closed
icinga-migration opened this issue Jun 22, 2016 · 4 comments
Labels
area/documentation End-user or developer help enhancement New feature or request

Comments

@icinga-migration
Copy link

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

Created by mfriedrich on 2016-06-22 12:28:09 +00:00

Assignee: (none)
Status: Closed (closed on 2016-07-07 12:47:38 +00:00)
Target Version: (none)
Last Update: 2016-07-07 12:47:38 +00:00 (in Redmine)

Backport?: Not yet backported
Include in Changelog: 0

states = [ OK, Warning ]

vs.

states = [ "OK", "Warning" ]

The latter works using the REST API.


Relations:

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-06-22 12:28:17 +00:00

  • Relates set to 11445

@icinga-migration
Copy link
Author

Updated by gbeutner on 2016-07-07 10:21:47 +00:00

  • Include in Changelog changed from 1 to 0

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-07-07 10:28:35 +00:00

  • Status changed from New to Assigned
  • Assigned to set to mfriedrich

Use strings.

@icinga-migration
Copy link
Author

Updated by gbeutner on 2016-07-07 12:47:38 +00:00

  • Status changed from Assigned to Closed
  • Assigned to deleted mfriedrich
  • Target Version deleted 2.5.0

@icinga-migration icinga-migration added enhancement New feature or request area/documentation End-user or developer help labels Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation End-user or developer help enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant