You have the following:

$history{ $+{ ticket } }{ $entry->{ action } } = {
                                     date  => $words[0],
                                    'time' => $words[1],
  ( exists ( $+{ order } ) ? (       order => $+{ order } ) : () ),
  ( exists ( $+{ invoice } ) ? (   invoice => $+{ invoice } ) : () ),
  ( exists ( $+{ shipment } ) ? ( shipment => $+{ shipment } ) : () ),
  ( exists ( $+{ scheduled_date } ) ? (
                            scheduled_date => $+{ scheduled_date } ) : () ),
  ( exists ( $+{ status } ) ? (     status => $+{ status } ) : () ),
};

That's a lot less readable than then following:

$history{ $+{ ticket } }{ $entry->{ action } } = {
                                     date           => $words[0],
                                     time           => $words[1],
  ( exists( $+{ order          } ) ? order          => $+{ order          } : () ),
  ( exists( $+{ invoice        } ) ? invoice        => $+{ invoice        } : () ),
  ( exists( $+{ shipment       } ) ? shipment       => $+{ shipment       } : () ),
  ( exists( $+{ scheduled_date } ) ? scheduled_date => $+{ scheduled_date } : () ),
  ( exists( $+{ status         } ) ? status         => $+{ status         } : () ),
};

It can be further cleaned using a loop.

$history{ $+{ ticket } }{ $entry->{ action } } = {
   date => $words[0],
   time => $words[1],
   (\%+)->%{ grep exists( $+{ $_ } ), qw(
      order
      invoice
      shipment
      scheduled_date
      status
   ) }
};
[download]

The mess can be hidden in a sub.

sub kv { my $h = shift; $h->%{ grep exists( $h->{ $_ } ), @_ } }

kv( \%+, qw( ... ) )
[download]

---

We can simplify further if we don't need 100% equivalence.

If you don't care about undef fields, it simplifies to the following:

$history{ $+{ ticket } }{ $entry->{ action } } = {
   date => $words[0],
   time => $words[1],
   (\%+)->%{qw(
      order
      invoice
      shipment
      scheduled_date
      status
   )}
};
[download]

If there are no extra captures (or you don't care if they end up as extra fields), it simplifies to the following:

$history{ $+{ ticket } }{ $entry->{ action } } = {
   date => $words[0],
   time => $words[1],
   %+,
};
[download]

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.