Skip to content

Releases: bestpractical/rtir

4.0.1

26 Jun 15:53
4.0.1

Choose a tag to compare

RTIR 4.0.1 - 2018-06-28

We're pleased to announce the general availability of RTIR 4.0.1. It contains
several improvements and also bugfixes. The list of changes included with this
release is below.

https://download.bestpractical.com/pub/rt/release/RT-IR-4.0.1.tar.gz
https://download.bestpractical.com/pub/rt/release/RT-IR-4.0.1.tar.gz.asc

SHA-256 sums

da942cd2e9facb65809518757b8b8ec010b83a140677f1a296c209b06f210b5e RT-IR-4.0.1.tar.gz
bd924a10710c03c17cc567d55d59c6e1c597d9b9190a01c1ebf04797b02e03c0 RT-IR-4.0.1.tar.gz.asc

General user UI

  • Fix charting to be inline with RT 4.4.1
  • Fix compatibility with RT's new status selector in search
  • Improve due and start date field widths on incident create (I#31870)
  • On RT 4.4.2, support new recently-viewed ticket feature (I#32484)
  • Improve alignment of Link and New buttons on Incident (I#31748)
  • Make Link, New, Take, Lookup buttons on IRs smaller
  • Respect rich-text input preference on incident pages (I#32166)
  • Fix Show Email link when show history pref is set to "immediate"
  • Include the new RTIR logo
  • Add button to save whois and traceroute results to ticket (I#31257)
  • Remove extra ?id= in transaction history links (I#30744)
  • Remove Type arg from call to UpdateData to load correct editor on Incidents
  • Add button to save Whois and Traceroute results to a ticket (I#31257)
  • Remove extra table row at bottom of RTIR ticket display
  • Restore styling for single column create/update layout
  • Provide a new option to use RT's search page directly rather than always
    redirecting to the RTIR search page
  • Add Lifecycle as an extra arg on Link
  • Update IPv6 matching to use stronger boundary conditions and avoid
    matches with non-IPv6 strings
  • Handle emails with +tags in 'Investigate to' MakeClicky links

Server Administration

  • Avoid dependency on Sort::Versions
  • Avoid regex deprecation warnings on perl 5.21.1+
  • Remove stale callback on upgrade from RTIR 3.2 that broke admin UI
    for ticket custom fields (I#32100)
  • Include RT 4.4.2 schema changes in the RTIR upgrade test
  • Remove unnecessary query debug log for Charts
  • Use Lifecycle to load queue-specific Formats
  • Wrap RT upgrade to catch warnings
  • During upgrades, correctly derive status from state CF for all cases
  • Only enable Net::Whois debug logs if RT's log level is debug

Developer

  • Add AfterWorked callback to /RTIR/Update.html
  • Add AfterHidden callback to /RTIR/Incident/Reply/index.html
  • Add AfterHidden callback to /RTIR/Incident/Create.html
  • Add ARGSRef and SaveChanges parameters to Initial callback on
    /RTIR/Edit.html
  • Add BeforeDisplay callback to /RTIR/Display.html
  • Add TicketObj parameter to BeforeDisplay callback on
    /RTIR/Incident/Create.html
  • Improve test compatibility with RT 4.4.2
  • Fix test failure with HTML::Mason versions prior to 1.52
  • Use RT's new version of SelectStatus
  • Remove unused EditComponentName callback file on upgraded systems
  • In RTIR/Update.html Initial callback, pass ARGS as a reference

Internals

  • Use RT::Handle's cmp_version function in upgrade version checks
  • Various fixes for perl 5.26 compatibility
  • Redirect to the correct display page from Update.html
  • Normalize SkipNotification checkbox value to an arrayref
  • Differentiate RTIR Reports menu from RT Reports in tests
  • Confirm TicketObj is defined before checking for queue whois server
  • Remove explicit require of Auth::Crypt that could cause errors when
    not installed
  • Stop parsing empty URIs to avoid warnings
  • Convert a queue name reference in tests to use lifecycle
  • When merging, default to empty string values for unset constituencies
  • In tests, use lexical iterator so inline test server can render articles
  • Filter CFs when creating Incident and Investigation at the same time

A complete changelog is available from git by running:
git log 4.0.0..4.0.1
or visiting
4.0.0...4.0.1

3.2.1

21 Jun 13:24

Choose a tag to compare

RTIR 3.2.1 - 2018-06-19

We're pleased to announce the general availability of RTIR 3.2.1. It
contains several improvements and also a few bug fixes. The list of
changes included with this release is below.

RTIR should always be run with the correct corresponding version of RT.
The 3.2.1 release runs best with RT 4.2.15. As noted in the upgrading
documentation, when upgrading, both RTIR and RT should be upgraded at
the same time.

https://download.bestpractical.com/pub/rt/release/RT-IR-3.2.1.tar.gz
https://download.bestpractical.com/pub/rt/release/RT-IR-3.2.1.tar.gz.asc

SHA-256 sums

331f11d915002ba8e8e0ebdd4e0f13feb70a0522b137cff31a8d7fefebb1f67e RT-IR-3.2.1.tar.gz
ee79b22b4efe6605b91e97644dbd21ea887308bf4dde1b1ac35e59abe3e9cf2c RT-IR-3.2.1.tar.gz.asc

General

  • The default MaxInlineBody is increased. It is still not unlimited by
    default because very large message bodies can cause performance issues
    with content that is automatically converted to links.
  • Update with a new RTIR logo.
  • Compatibility with Perl 5.26.1.

Bugs

  • Show only statuses applicable to the current queue when creating a new
    ticket.
  • Remove incorrect duplicate id parameters in links in ticket history.
  • Many fixes to various incorrect or failing tests and updates to align
    tests with changes in core RT.
  • Update two uses of the Mason redirect with RT's redirect which makes
    sure redirects work for all conditions including running on non-standard
    ports.
  • Correctly handle custom fields, including those in custom field groupings,
    to avoid warnings when creating an incident and investigation at the
    same time.

A complete changelog is available from git by running:
git log 3.2.0..3.2.1
or visiting
3.2.0...3.2.1

4.0.0

20 Jul 16:44
4.0.0

Choose a tag to compare

RTIR 4.0.0 - 2016-07-20

We're very excited to announce the availability of RTIR 4.0.0: the first
release for the next major version of RTIR. We have completely rearchitected
RTIR queues in order to significantly improve RTIR's flexibility and
performance. As this is a new major version number, with many changes
throughout the entire system, we urge you to carefully test your
configuration and customizations. Additionally, RTIR 4.0.0 is the first
release of RTIR compatible with RT 4.4.

A quick note on the version number: while this next version of RTIR was
under development, we had naturally labelled it RTIR 3.4. However, to
reflect the significant architectural changes we made for constituencies and
multiple queues, we decided to give this release a new major version number.
If you're looking for the version of RTIR compatible with RT 4.4, RTIR 4.0
is it!

If you are also upgrading to RT 4.4, be sure to also read its
documentation, available at
https://docs.bestpractical.com/rt/4.4/UPGRADING-4.4.html

https://download.bestpractical.com/pub/rt/release/RT-IR-4.0.0.tar.gz
https://download.bestpractical.com/pub/rt/release/RT-IR-4.0.0.tar.gz.asc

SHA1 sums

b660855cd7467cad1fec60b4050437dacb77cb91 RT-IR-4.0.0.tar.gz
f0d9051b250e1d29570e64cd8c6d78310aeb7f64 RT-IR-4.0.0.tar.gz.asc

A list of the major new features in RTIR 4.0.0 is included below. We'll be
describing and demoing these new features in a series of blog posts on
https://bestpractical.com/blog/ in the coming weeks.

  • Shawn M Moore, for Best Practical
    • The constituency system has been completely redesigned from the ground
      up. Don't worry, your existing constituencies will be migrated as part
      of the upgrade. Now constituencies get a full-fledged queue for each
      stage of the incident response workflow (one for each of reports,
      incidents, investigations, and countermeasures). This lets constituency
      queues tap into much more of RT's flexibility around custom fields,
      watchers, scrips, etc. This addresses many longstanding limitations
      around the previous constituency queue design, and significantly
      improves performance as well.
    • You may now have multiple queues for each type of RTIR queue:
      multiple Incident Report queues, multiple Incident queues, etc. Each of
      these queues may have its own custom fields, watchers, permissions,
      scrips, templates, and so on. We're excited to hear about how you make
      use of this new flexibility.
    • If a user has permissions to work with multiple constituencies, it is
      now possible to limit RTIR's web interface to a single constituency
      by clicking a link from the new "Work with constituency" box on the RTIR
      homepage.
    • Blocks have been renamed to Countermeasures to reflect their more
      generic use case.

There were many, many changes throughout RTIR to support these major new
features. Here is an abbreviated list of additional changes:

General user UI

  • The main navigation menu for RTIR has been rearranged; RT's menus have
    been moved to underneath the RT heading.
  • Maintain message format when launching an Investigation (I#30786)
  • IPs, email addresses, etc which are annotated with buttons in messages
    now look like buttons (I#31259)
  • Clean up the visual design of the Lookup tool page
  • Make the blue header bar darker to hint you're within RTIR (I#31297)
  • It is currently no longer possible to simultaneously launch an
    Investigation on the Incident creation page due to the new architecture
  • Fix lowercase lifecycle display names on Lookup tool
  • Fix grammar error in Lookup tool
  • Improve support for infinite scroll (I#32137)
  • Fix broken attachment download links under infinite scroll (I#32084)
  • Suppress lookup and other RTIR auto linking in SelfService (I#31868)
  • Avoid error when all queues of a type are disabled
  • Avoid double concatenation of ?id=X on txn anchors
  • Allow users to set SLA on create, view the value, and update (I#32167)
  • Fix Search Builder submit for non-root WebPath

Command-line

  • add_constituency now produces less output in the ordinary case, but if
    you want to see every change it makes, you can pass the new --verbose flag

Mail

  • X-RT-Mail-Extension no longer sets constituency; instead you can now use
    ordinary RT features to filter incoming mail into the correct queue

Web Administration

  • DutyTeams now have the ForwardMessage right by default
  • Different queues may now have a different default whois server,
    controlled by the "RTIR default WHOIS server" custom field

Server Administration

  • $MaxInlineBody's default has changed from unlimited, which can cause
    performance issues, to 25kb
  • Bail out from make initdb early if RT::IR isn't in Plugins (I#31961)
  • Update required RT version from 4.4.0 to 4.4.1 (I#32093)

Developer

  • Many of the methods in RTIR's codebase now produce explicit return
    values
  • RT::IR::FlushCustomFieldsCache is now a supported API
  • RT::IR::Test::Web's unused merge_ticket method has been removed
  • The guts of bin/add_constituency have been factored out into an
    RT::IR::ConstituencyManager which makes it much easier to create
    constituencies programmatically
  • Added a RT::IR->HREFTo helper function which maintains the user's
    currently-selected constituency
  • Innumerable API changes were made to support RTIR's constituency queues
  • The Lookup tool page now has four callbacks (BeforeCurrent,
    AfterCurrent, BeforeTools, AfterTools)
  • The body HTML tag now has an "rtir" class to aid in styling

Documentation

  • Fix several POD errors
  • Improve clarity around RTIR install instructions

A complete changelog is available from git by running:
git log 3.2.0..4.0.0
or visiting
3.2.0...4.0.0