[Rt-commit] rt branch, 4.4/dashboard-user-context, repushed

? sunnavy sunnavy at bestpractical.com
Wed Oct 17 15:56:25 EDT 2018


The branch 4.4/dashboard-user-context was deleted and repushed:
       was 178384e3b0f89038b795a80ee4436f222369a8ac
       now f10597b4167a1e5a8e5a4ba2c28b27dd6ab70af6

1: 178384e3b ! 1: f10597b41 Support to generate different dashboard content for each recipient
    @@ -63,11 +63,7 @@
      
          if ($args{DryRun}) {
              print << "SUMMARY";
    -     Dashboard: @{[ $dashboard->Name ]}
    --    User:   @{[ $currentuser->Name ]} <$args{Email}>
    -+    User:   @{[ $context_user->Name ]} <$args{Email}>
    - SUMMARY
    -         return;
    +@@
          }
      
          local $HTML::Mason::Commands::session{CurrentUser} = $currentuser;
    @@ -124,19 +120,23 @@
      </table>
      </&>
      
    -+<&| /Widgets/TitleBox, title => loc('Content Context') &>
    ++<&| /Widgets/TitleBox, title => loc('Search Context') &>
     +
     +<p class="description">
    -+<&|/l&>For searches like "10 highest priority tickets I own" that contain __CurrentUser__ in the query, the results are various for differnet users. For dashboards containing such searches, you might want to generate different content for each recipient who is assumed to be __CurrentUser__ in the query. Tick "Each dashboard recipient" for cases like that.</&>
    ++<&|/l&>Most searches show the same results for all users and can be run as the user who owns the dashboard subscription (Subscription owner).</&>
    ++</p>
    ++
    ++<p class="description">
    ++<&|/l&>For searches like "10 highest priority tickets I own" that contain __CurrentUser__ in the query, the results are specific to each recipient. For dashboards with these searches, select "Each dashboard recipient" below to run each search with the recipient set as the "Current User".</&>
     +</p>
     +
     +<table>
     +    <tr><td class="label"><&|/l&>Run Dashboard Searches As</&>:</td>
     +        <td>
    -+            <input type="radio" id="context-subscriber" name="Context" value="subscriber" <% $fields{'Context'} eq 'subscriber' ? 'checked="checked"' : "" |n %>></input>
    -+            <label for="context-subscriber"><&|/l&>Dashboard subscriber</&>(<% $session{CurrentUser}->Name %>)</label>
    ++            <input type="radio" id="context-subscriber" name="Context" value="subscriber" <% ($fields{'Context'} // '') ne 'recipient' ? 'checked="checked"' : "" |n %>></input>
    ++            <label for="context-subscriber"><&|/l&>Subscription owner</&>(<% $session{CurrentUser}->Name %>)</label>
     +            <br />
    -+            <input type="radio" id="context-recipient" name="Context" value="recipient" <% $fields{'Context'} eq 'recipient' ? 'checked="checked"' : "" |n %>></input>
    ++            <input type="radio" id="context-recipient" name="Context" value="recipient" <% ($fields{'Context'} // '') eq 'recipient' ? 'checked="checked"' : "" |n %>></input>
     +            <label for="context-recipient"><&|/l&>Each dashboard recipient</&></label>
     +        </td>
     +    </tr>



More information about the rt-commit mailing list