Log inSkip to main contentSkip to sidebar
Loading…
Puppet Tickets
  • Dashboards
  • Projects
  • Issues
  • Give feedback to Atlassian
  • Help
    • Jira Core help
    • Keyboard Shortcuts
    • About Jira
    • Jira Credits
  • Log In

Export - CSV (All fields)

Export - CSV (Current fields)

Comma (,) Semicolon (;) Vertical bar (|) Caret (^)

  1. Bug FACT-3007
    Facter 4 outputs hypervisors facts differently on Amazon 7
  2. Bug FACT-3004
    Do not auto promote dotted facts to structured
  3. Bug FACT-2999
    Facter cannot autoload provider from stdlib inside puppetserver repl
  4. Bug FACT-2998
    Facter breaks when querying for custom facts
  5. Bug FACT-2997
    Domain fact cannot be resolved on travis without ffi
  6. Bug FACT-2996
    Performance regression gathering networking facts in facter 4.x
  7. Bug FACT-2994
    selinux fact is not properly detected by Facter 4
  8. Bug FACT-2993
    Facter 4.0.52 does not provide trusted['hostname'] in Docker environments
  9. Bug FACT-2989
    Facter 4.0.52 does not return fqdn fact
  10. Bug FACT-2988
    Facter takes 20+ seconds on Windows due to azure metadata query
  11. Bug FACT-2987
    Facter 4 outputs hypervisors.zone.id fact differently on Solaris
  12. Bug FACT-2986
    Facter 4 outputs virtual fact differently on Amazon 6
  13. Bug FACT-2984
    Facter 4 outputs mountpoints facts differently on macOS
  14. Bug FACT-2983
    Facter 4 outputs ldom facts differently on Solaris SPARC
  15. Bug FACT-2982
    Facter 4 outputs mountpoints facts differently on Solaris
  16. Bug FACT-2981
    Loopback IPv6 ip is not returned correctly
  17. Bug FACT-2967
    Facter 4 outputs several facts with different precision than Facter 3
  18. Bug FACT-2966
    Facter 4 outputs some uptime facts differently on Windows
  19. Bug FACT-2965
    Facter 4 outputs the processors.speed fact differently on AIX
  20. Bug FACT-2956
    Facter should ensure core facts are resolved before loading custom facts
  21. Bug FACT-2946
    VLAN interfaces not properly discovered
  22. Bug FACT-2930
    Inconsistent handling of Date types in custom facts
Refresh results
{"errorMessages":["jqlTooComplex"],"errors":{}}
[{"id":-1,"name":"My open issues","jql":"assignee = currentUser() AND resolution = Unresolved order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-2,"name":"Reported by me","jql":"reporter = currentUser() order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-4,"name":"All issues","jql":"order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-5,"name":"Open issues","jql":"resolution = Unresolved order by priority DESC,updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-9,"name":"Done issues","jql":"statusCategory = Done order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-3,"name":"Viewed recently","jql":"issuekey in issueHistory() order by lastViewed DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-6,"name":"Created recently","jql":"created >= -1w order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-7,"name":"Resolved recently","jql":"resolutiondate >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-8,"name":"Updated recently","jql":"updated >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false}]
0.3
0
  • Atlassian Jira Project Management Software
  • About Jira
  • Report a problem

Atlassian