[Bps-public-commit] rt-extension-assets branch, 1.0/tutorial, updated. 09c1100afdbf411f32ae308fd2cacd049496553d
Alex Vandiver
alexmv at bestpractical.com
Thu Dec 26 18:46:41 EST 2013
The branch, 1.0/tutorial has been updated
via 09c1100afdbf411f32ae308fd2cacd049496553d (commit)
via 115ad65002a58e5d4a7cf9af289324675fa484bf (commit)
via 6a1e006b0d238df10b26ec352da2f846a6fb5171 (commit)
via 097abb59990a4e3738e2259b194a7a0ab777c827 (commit)
via f9dfafb72c277f084895234e93e1b8bcd3efc306 (commit)
via c82ca516f10876840a987303db0dc86e040593c7 (commit)
via 1d6f0871b7643ba587809ef4dea0f5046858356d (commit)
from 8d065123403bd3d96f6609307536845c9504dc56 (commit)
Summary of changes:
lib/RT/Extension/Assets/Tutorial.pm | 303 ++++++++++++++++++------------------
1 file changed, 151 insertions(+), 152 deletions(-)
- Log -----------------------------------------------------------------
commit 1d6f0871b7643ba587809ef4dea0f5046858356d
Author: Alex Vandiver <alexmv at bestpractical.com>
Date: Thu Dec 26 18:29:42 2013 -0500
Trailing "1;" is unnecessary, and shows up in POD
diff --git a/lib/RT/Extension/Assets/Tutorial.pm b/lib/RT/Extension/Assets/Tutorial.pm
index 0dd2838..a71fd73 100644
--- a/lib/RT/Extension/Assets/Tutorial.pm
+++ b/lib/RT/Extension/Assets/Tutorial.pm
@@ -325,4 +325,4 @@ help you track assets. There are many more features you'll find as you explore
the assets interface, like stacking multiple assets on a single ticket, bulk
update features similar to tickets, and the search interface. Have fun!
-1;
+=cut
commit c82ca516f10876840a987303db0dc86e040593c7
Author: Alex Vandiver <alexmv at bestpractical.com>
Date: Thu Dec 26 18:30:59 2013 -0500
Unwrap incorrectly wrapped link
diff --git a/lib/RT/Extension/Assets/Tutorial.pm b/lib/RT/Extension/Assets/Tutorial.pm
index a71fd73..0668ac3 100644
--- a/lib/RT/Extension/Assets/Tutorial.pm
+++ b/lib/RT/Extension/Assets/Tutorial.pm
@@ -41,8 +41,8 @@ extensions, first add C<RT::Extension::Assets> to your C<@Plugins> line.
There are a few configuration options you might set before starting. Assets
offers a C<$DefaultCatalog> feature that works similar to RT's
-L<DefaultQueue|http://bestpractical.com/docs/rt/latest/RT_Config.html#DefaultQue
-ue>, but you can probably skip it for now since you don't have any catalogs yet.
+L<DefaultQueue|http://bestpractical.com/docs/rt/latest/RT_Config.html#DefaultQueue>,
+but you can probably skip it for now since you don't have any catalogs yet.
More interesting are some optional portlets you can activate to add asset data
to RT's pages. MyAssets and FindAsset portlets are available for placement on
commit f9dfafb72c277f084895234e93e1b8bcd3efc306
Author: Alex Vandiver <alexmv at bestpractical.com>
Date: Thu Dec 26 18:32:08 2013 -0500
Trim trailing whitespace
diff --git a/lib/RT/Extension/Assets/Tutorial.pm b/lib/RT/Extension/Assets/Tutorial.pm
index 0668ac3..270820e 100644
--- a/lib/RT/Extension/Assets/Tutorial.pm
+++ b/lib/RT/Extension/Assets/Tutorial.pm
@@ -1,141 +1,141 @@
=head1 Introduction
-This is a basic tutorial for setting up asset tracking in RT using Best
-Practical's Assets extension. At the end, you'll have a basic configuration
+This is a basic tutorial for setting up asset tracking in RT using Best
+Practical's Assets extension. At the end, you'll have a basic configuration
that lets you add assets, search for them, link them to tickets, etc.
=begin HTML
-<p><img src="http://static.bestpractical.com/images/assets/asset-search.png"
+<p><img src="http://static.bestpractical.com/images/assets/asset-search.png"
alt="Asset Search Results" /></p>
=end HTML
-You can follow along with the tutorial and try setting things up yourself to
-get a feel for all of the administrative controls. If you want to get a jump
-start, the files to set up this basic configuration are provided in the
-L<RT::Extension::Assets> distribution in the F<etc> directory. For
-configuration, look in F<etc/Tutorial_Configuration.txt>. You can copy all or
+You can follow along with the tutorial and try setting things up yourself to
+get a feel for all of the administrative controls. If you want to get a jump
+start, the files to set up this basic configuration are provided in the
+L<RT::Extension::Assets> distribution in the F<etc> directory. For
+configuration, look in F<etc/Tutorial_Configuration.txt>. You can copy all or
part and paste it in your F<RT_SiteConfig.pm>.
-To load the test catalog, custom fields, and users, add
-C<RT::Extension::Assets> to your C<@Plugins> line after installing, then run
+To load the test catalog, custom fields, and users, add
+C<RT::Extension::Assets> to your C<@Plugins> line after installing, then run
the following from your RT directory:
sbin/rt-setup-database --action insert --datafile \
local/plugins/RT-Extension-Assets/etc/tutorialdata
-This will change the default catalog name, create some users, and give those
-users asset permissions. Only asset rights are granted, so you need to grant
-additional rights if you want to experiment with creating tickets and linking
-assets. The initial user passwords are 'password'. You should only run this on
-a test RT instance as it is not intended to be used for configuring a
+This will change the default catalog name, create some users, and give those
+users asset permissions. Only asset rights are granted, so you need to grant
+additional rights if you want to experiment with creating tickets and linking
+assets. The initial user passwords are 'password'. You should only run this on
+a test RT instance as it is not intended to be used for configuring a
production system.
=head1 Getting Started
-Install the extension following the instructions and some new tables will be
-added to your RT database and the assets code will be installed. As with all
+Install the extension following the instructions and some new tables will be
+added to your RT database and the assets code will be installed. As with all
extensions, first add C<RT::Extension::Assets> to your C<@Plugins> line.
-There are a few configuration options you might set before starting. Assets
-offers a C<$DefaultCatalog> feature that works similar to RT's
+There are a few configuration options you might set before starting. Assets
+offers a C<$DefaultCatalog> feature that works similar to RT's
L<DefaultQueue|http://bestpractical.com/docs/rt/latest/RT_Config.html#DefaultQueue>,
but you can probably skip it for now since you don't have any catalogs yet.
-More interesting are some optional portlets you can activate to add asset data
-to RT's pages. MyAssets and FindAsset portlets are available for placement on
-RT at a Glance or in dashboards and a UserAssets portlet is available for the
+More interesting are some optional portlets you can activate to add asset data
+to RT's pages. MyAssets and FindAsset portlets are available for placement on
+RT at a Glance or in dashboards and a UserAssets portlet is available for the
user summary pages.
-These portlets are fairly self-explanitory and you can add them by finding
-C<$HomepageComponents> and C<@UserSummaryPortlets> respectively in
-F<RT_Config.pm>, copying to F<RT_SiteConfig.pm>, and adding the portlets you
-want. There are also examples in the tutorial sample configuration file. Note
-that C<$HomepageComponents> makes the portlets available, but doesn't put them
-on RT at a Glance. To add them, just click the Edit link on the upper righthand
-corner of the homepage. C<@UserSummaryPortlets> does automatically add the
-"Assigned Assets" portlet to the User Summary page. It will appear based on the
-position in the configuration, so just place it in the list where you want it
+These portlets are fairly self-explanitory and you can add them by finding
+C<$HomepageComponents> and C<@UserSummaryPortlets> respectively in
+F<RT_Config.pm>, copying to F<RT_SiteConfig.pm>, and adding the portlets you
+want. There are also examples in the tutorial sample configuration file. Note
+that C<$HomepageComponents> makes the portlets available, but doesn't put them
+on RT at a Glance. To add them, just click the Edit link on the upper righthand
+corner of the homepage. C<@UserSummaryPortlets> does automatically add the
+"Assigned Assets" portlet to the User Summary page. It will appear based on the
+position in the configuration, so just place it in the list where you want it
to appear.
-Once you have your configuration complete, restart your server and you're ready
+Once you have your configuration complete, restart your server and you're ready
to go.
=head1 Catalogs
-For the initial configuration, we'll log in as RT's root user so we have full
-rights on the asset configuration. You could also create an "Asset Admin" group
+For the initial configuration, we'll log in as RT's root user so we have full
+rights on the asset configuration. You could also create an "Asset Admin" group
and assign appropriate rights to allow other users to manage catalogs.
-When you log in you'll see a new Assets menu, but before looking there we need
-to look at catalogs and some other configuration. Catalogs are to assets what
-queues are to tickets, so if you've used RT, the relationship should be fairly
-familiar. Similar to the General queue, a "General assets" catalog is provided
+When you log in you'll see a new Assets menu, but before looking there we need
+to look at catalogs and some other configuration. Catalogs are to assets what
+queues are to tickets, so if you've used RT, the relationship should be fairly
+familiar. Similar to the General queue, a "General assets" catalog is provided
to get you started. You can see it at Admin > Assets > Catalogs.
-We're going to use the default, but change it to a name more appropriate for
-our use. Clicking on the asset name brings us to the catalog edit page and we
-can update the name to "IT Department Assets". You can update the description
+We're going to use the default, but change it to a name more appropriate for
+our use. Clicking on the asset name brings us to the catalog edit page and we
+can update the name to "IT Department Assets". You can update the description
if you like as well.
=begin HTML
-<p><img src="http://static.bestpractical.com/images/assets/edit-catalog.png"
+<p><img src="http://static.bestpractical.com/images/assets/edit-catalog.png"
alt="Edit Catalog" /></p>
=end HTML
-You'll also notice that catalogs have a lifecycle just like queues. The assets
-extension comes with a default assets lifecycle, but just like queues you can
-create new ones with custom statuses and other configuration to allow RT to
+You'll also notice that catalogs have a lifecycle just like queues. The assets
+extension comes with a default assets lifecycle, but just like queues you can
+create new ones with custom statuses and other configuration to allow RT to
reflect the states of your assets.
-You can find the asset lifecycle in the asset configuration file in your RT
+You can find the asset lifecycle in the asset configuration file in your RT
installation at:
local/plugins/RT-Extension-Assets/etc/Assets_Config.pm
-The initial statuses are new, allocated, in-use, recycled, stolen, and deleted.
-Depending on your process, you might add new ones like surplussed, donated, or
-in-repair. To create a new asset lifecycle, just copy the default into
-F<RT_SiteConfig.pm>, replace the top-level "assets" key with a new name, and
+The initial statuses are new, allocated, in-use, recycled, stolen, and deleted.
+Depending on your process, you might add new ones like surplussed, donated, or
+in-repair. To create a new asset lifecycle, just copy the default into
+F<RT_SiteConfig.pm>, replace the top-level "assets" key with a new name, and
make your changes.
=head1 Asset Custom Fields
-Next we need to create some custom fields to hold our asset metadata. You can
-find asset custom fields at Admin > Assets > Custom Fields and they work just
+Next we need to create some custom fields to hold our asset metadata. You can
+find asset custom fields at Admin > Assets > Custom Fields and they work just
like custom fields for other RT objects.
=begin HTML
-<p><img src="http://static.bestpractical.com/images/assets/asset-cfs.png"
+<p><img src="http://static.bestpractical.com/images/assets/asset-cfs.png"
alt="Asset Custom Fields" /></p>
=end HTML
-The extension will automatically provide some core values for your assets. Each
-asset can have a Name and Description and, like tickets, they have statuses
-based on the lifecycle configuration. You can use Name and Description however
-you want and they are not required. However, many of the asset pages use these
-fields so it's best to provide a descriptive name to make it easy for people
-working in RT to identify the asset quickly. The manufacturer's product name
+The extension will automatically provide some core values for your assets. Each
+asset can have a Name and Description and, like tickets, they have statuses
+based on the lifecycle configuration. You can use Name and Description however
+you want and they are not required. However, many of the asset pages use these
+fields so it's best to provide a descriptive name to make it easy for people
+working in RT to identify the asset quickly. The manufacturer's product name
can be convenient (e.g., '15" Macbook Pro').
-Assets come with three user fields you can associate with an asset: Owner, Held
-By, and Contact. These are provided to cover different types of assets, from
-laptops to servers to software, and different asset management situations.
-Owner can hold the user who bought the asset, maybe the head of the department
-where the budget came from. Held by is who the asset is assigned to. Laptops
-are assigned to a user and servers might be held (or managed) by the system
-administrators. Contact can be used to set a manager who might need to know
-about needed system updates or equipment with expiring support. Like tickets,
-these roles give you places to attach rights, so use them however they work
+Assets come with three user fields you can associate with an asset: Owner, Held
+By, and Contact. These are provided to cover different types of assets, from
+laptops to servers to software, and different asset management situations.
+Owner can hold the user who bought the asset, maybe the head of the department
+where the budget came from. Held by is who the asset is assigned to. Laptops
+are assigned to a user and servers might be held (or managed) by the system
+administrators. Contact can be used to set a manager who might need to know
+about needed system updates or equipment with expiring support. Like tickets,
+these roles give you places to attach rights, so use them however they work
best for you.
-Any other information you want to track will need custom fields. We'll start
+Any other information you want to track will need custom fields. We'll start
with a few basic fields:
=over
@@ -146,8 +146,8 @@ The serial number from the asset.
=item * Tracking Number (enter one value)
-An internal tracking number. RT will assign an asset ID as well, but you may
-have other systems to integrate with or already have a way to assign asset ids
+An internal tracking number. RT will assign an asset ID as well, but you may
+have other systems to integrate with or already have a way to assign asset ids
for accounting purposes.
=item * Manufacturer (dropdown)
@@ -162,8 +162,8 @@ Is it a laptop, server, or cell phone?
When the asset was given to the owner (or held by) person.
-Assets keep a transaction history like tickets, so you may be able pull this
-information from the "owner set to X" transaction. Creating a separate field
+Assets keep a transaction history like tickets, so you may be able pull this
+information from the "owner set to X" transaction. Creating a separate field
makes it easier to report on.
=item * Support Expiration (date)
@@ -174,10 +174,10 @@ When the current support contract expires.
=head1 Custom Field Grouping
-Any custom fields you create will be displayed on the asset display page in a
-default "Custom Fields" section. That may be sufficient, but assets also
-supports RT's new custom field grouping feature, so we can group together some
-similar custom fields and give them a custom name. If we add the following to
+Any custom fields you create will be displayed on the asset display page in a
+default "Custom Fields" section. That may be sufficient, but assets also
+supports RT's new custom field grouping feature, so we can group together some
+similar custom fields and give them a custom name. If we add the following to
F<RT_SiteConfig.pm>:
Set(%CustomFieldGroupings,
@@ -188,141 +188,141 @@ F<RT_SiteConfig.pm>:
},
);
-and restart RT, the dates will be tacked on the end of the Dates portlet and we
+and restart RT, the dates will be tacked on the end of the Dates portlet and we
get an Asset Details label on the other custom fields.
=begin HTML
-<p><img
-src="http://static.bestpractical.com/images/assets/asset-date-details.png"
+<p><img
+src="http://static.bestpractical.com/images/assets/asset-date-details.png"
alt="Asset Date and Details Display" /></p>
=end HTML
=head1 Asset Rights
-Now we've got the basic configuration in place to start recording asset data.
-Next we need to assign some rights so people can view and edit asset
-information. Our staff are all privileged users so we'll grant all view and
-modify rights on our catalog to the Privileged role. We'll also include rights
-to view and modify the catalog's custom fields, although you could set these
-rights individually on each custom field if you wanted to allow users to see
+Now we've got the basic configuration in place to start recording asset data.
+Next we need to assign some rights so people can view and edit asset
+information. Our staff are all privileged users so we'll grant all view and
+modify rights on our catalog to the Privileged role. We'll also include rights
+to view and modify the catalog's custom fields, although you could set these
+rights individually on each custom field if you wanted to allow users to see
some but not others.
-Similar to queues, you can set rights at the catalog level. Go to Admin >
-Assets > Catalogs and click on the catalog you want to edit. Click Group Rights
-in the submenu to assign asset rights to groups like the system Privileged
+Similar to queues, you can set rights at the catalog level. Go to Admin >
+Assets > Catalogs and click on the catalog you want to edit. Click Group Rights
+in the submenu to assign asset rights to groups like the system Privileged
group.
=begin HTML
-<p><img src="http://static.bestpractical.com/images/assets/catalog-rights.png"
+<p><img src="http://static.bestpractical.com/images/assets/catalog-rights.png"
alt="Catalog Rights" /></p>
=end HTML
-We also want unprivileged users to be able to see their own assets to make it
-easier to submit support requests. To give them just the Name and Description
-on their own assets, we can grant SeeAssets and SeeCatalogs on the catalog to
+We also want unprivileged users to be able to see their own assets to make it
+easier to submit support requests. To give them just the Name and Description
+on their own assets, we can grant SeeAssets and SeeCatalogs on the catalog to
the Held By role.
-All of the asset rights are described in the Assets documentation. You can get
-much more detailed and fine-grained than this example, allowing selected groups
-and users to view and modify multiple different asset custom fields across many
+All of the asset rights are described in the Assets documentation. You can get
+much more detailed and fine-grained than this example, allowing selected groups
+and users to view and modify multiple different asset custom fields across many
different catalogs.
=head1 Working with Assets
-So now that we have all of that configuration done, what can we do? Here are a
+So now that we have all of that configuration done, what can we do? Here are a
few scenarios to give you some ideas.
=head2 Add Assets to Your Catalogs
-To start, staff can now start adding assets to RT allowing you to manage what
-you have, what state it's in, who currently has it, and when support expires.
-You could set up an intake process to get new assets added as they come in, and
-eventually have statuses updated as they are assigned, used, and eventually
+To start, staff can now start adding assets to RT allowing you to manage what
+you have, what state it's in, who currently has it, and when support expires.
+You could set up an intake process to get new assets added as they come in, and
+eventually have statuses updated as they are assigned, used, and eventually
cycled out.
-If you already have an asset database, even something simple like a
-spreadsheet, you may be able to do an initial bulk import. Best Practical has
-released L<RT::Extension::Assets::Import::CSV> which is a CSV import tool to
+If you already have an asset database, even something simple like a
+spreadsheet, you may be able to do an initial bulk import. Best Practical has
+released L<RT::Extension::Assets::Import::CSV> which is a CSV import tool to
help you with this.
=head2 Track Assets
-Your staff can now easily track work on assets by linking RT tickets to the
-assets. Assume you have an issue with an asset, like a server needs a new power
-supply. Your staff can use the asset search page to find the server. You'll
-notice that the RT search box is context sensitive, so when you're on an asset
+Your staff can now easily track work on assets by linking RT tickets to the
+assets. Assume you have an issue with an asset, like a server needs a new power
+supply. Your staff can use the asset search page to find the server. You'll
+notice that the RT search box is context sensitive, so when you're on an asset
page, the search changes to Search Assets and you can search with that as well.
-Once you locate the server asset record, in the Actions menu you'll find
-"Create linked ticket", which does just that. You select the queue and which
-user to use from the asset as the Requestor, and you land on the ticket create
+Once you locate the server asset record, in the Actions menu you'll find
+"Create linked ticket", which does just that. You select the queue and which
+user to use from the asset as the Requestor, and you land on the ticket create
page with some information pre-filled.
=begin HTML
-<p><img
-src="http://static.bestpractical.com/images/assets/asset-ticket-create.png"
+<p><img
+src="http://static.bestpractical.com/images/assets/asset-ticket-create.png"
alt="Create Ticket for Asset Work" /></p>
=end HTML
-As you can see in the screenshot, when you create a ticket with a linked asset,
-you get an asset portlet on the create page and on the ticket display page as
-well. If you navigate back to the asset, you'll see a link back to the ticket
-in the Links section there. This gives you a record of all the tickets that
-have been opened against this asset. If this is a common scenario for you, you
-might even add a custom field on the ticket with the vendor tracking number of
-the repair. During the repair, you might flip the asset to an 'in-repair'
+As you can see in the screenshot, when you create a ticket with a linked asset,
+you get an asset portlet on the create page and on the ticket display page as
+well. If you navigate back to the asset, you'll see a link back to the ticket
+in the Links section there. This gives you a record of all the tickets that
+have been opened against this asset. If this is a common scenario for you, you
+might even add a custom field on the ticket with the vendor tracking number of
+the repair. During the repair, you might flip the asset to an 'in-repair'
status. Then when the ticket is resolved, flip it back to 'in-use'.
=head2 End User Asset Tickets
-If an end user contacts us with some problems with their laptop, RT makes it
-easy to find the correct laptop record and create a ticket for them. Since our
-support staff do this frequently, they have added the Find User portlet to
-their RT at a glance page and can quickly search for the user and go to their
+If an end user contacts us with some problems with their laptop, RT makes it
+easy to find the correct laptop record and create a ticket for them. Since our
+support staff do this frequently, they have added the Find User portlet to
+their RT at a glance page and can quickly search for the user and go to their
User Summary page (new in RT 4.2).
-We have added the Assigned Assets portlet to the User Summary page, so the
-laptop is right there on the page when we find the user. We can just click on
-the asset, then use the "Create linked ticket" action as before to create the
+We have added the Assigned Assets portlet to the User Summary page, so the
+laptop is right there on the page when we find the user. We can just click on
+the asset, then use the "Create linked ticket" action as before to create the
new repair ticket.
=head2 End User Self Service
-Assume we already assign passwords to our unprivileged users so they can use
-RT's self service interface to submit tickets and they have basic permissions
-to do so (SeeQueue on the designated queue, CreateTicket, etc.). Since we've
-given some asset rights to unprivileged users, they can use RT's Self Service
-interface to find their assets (e.g., laptops, cell phones, etc.) when
+Assume we already assign passwords to our unprivileged users so they can use
+RT's self service interface to submit tickets and they have basic permissions
+to do so (SeeQueue on the designated queue, CreateTicket, etc.). Since we've
+given some asset rights to unprivileged users, they can use RT's Self Service
+interface to find their assets (e.g., laptops, cell phones, etc.) when
submitting support requests.
-When they log into the self service interface, they will see an Assets menu
-that takes them to a page displaying assets assigned to them. In our example
-configuration, this is based on the Held by setting we set when we gave out the
-laptop. When they navigate to the asset, they will see the Actions menu with
-the same "Create linked ticket" action our staff uses. When they click on that,
-they'll end up on the simplified ticket create page for self service. When the
-ticket is created, the laptop will already be linked to it, saving our staff
+When they log into the self service interface, they will see an Assets menu
+that takes them to a page displaying assets assigned to them. In our example
+configuration, this is based on the Held by setting we set when we gave out the
+laptop. When they navigate to the asset, they will see the Actions menu with
+the same "Create linked ticket" action our staff uses. When they click on that,
+they'll end up on the simplified ticket create page for self service. When the
+ticket is created, the laptop will already be linked to it, saving our staff
the work.
=begin HTML
-<p><img
-src="http://static.bestpractical.com/images/assets/asset-ticket-create.png"
+<p><img
+src="http://static.bestpractical.com/images/assets/asset-ticket-create.png"
alt="Create Ticket for Asset Work" /></p>
=end HTML
=head1 Summary
-This tutorial is only a quick overview showing how the assets extension can
-help you track assets. There are many more features you'll find as you explore
-the assets interface, like stacking multiple assets on a single ticket, bulk
+This tutorial is only a quick overview showing how the assets extension can
+help you track assets. There are many more features you'll find as you explore
+the assets interface, like stacking multiple assets on a single ticket, bulk
update features similar to tickets, and the search interface. Have fun!
=cut
commit 097abb59990a4e3738e2259b194a7a0ab777c827
Author: Alex Vandiver <alexmv at bestpractical.com>
Date: Thu Dec 26 18:36:46 2013 -0500
Typo fixes
diff --git a/lib/RT/Extension/Assets/Tutorial.pm b/lib/RT/Extension/Assets/Tutorial.pm
index 270820e..3cfd442 100644
--- a/lib/RT/Extension/Assets/Tutorial.pm
+++ b/lib/RT/Extension/Assets/Tutorial.pm
@@ -49,12 +49,12 @@ to RT's pages. MyAssets and FindAsset portlets are available for placement on
RT at a Glance or in dashboards and a UserAssets portlet is available for the
user summary pages.
-These portlets are fairly self-explanitory and you can add them by finding
+These portlets are fairly self-explanatory and you can add them by finding
C<$HomepageComponents> and C<@UserSummaryPortlets> respectively in
F<RT_Config.pm>, copying to F<RT_SiteConfig.pm>, and adding the portlets you
want. There are also examples in the tutorial sample configuration file. Note
that C<$HomepageComponents> makes the portlets available, but doesn't put them
-on RT at a Glance. To add them, just click the Edit link on the upper righthand
+on RT at a Glance. To add them, just click the Edit link on the upper right-hand
corner of the homepage. C<@UserSummaryPortlets> does automatically add the
"Assigned Assets" portlet to the User Summary page. It will appear based on the
position in the configuration, so just place it in the list where you want it
commit 6a1e006b0d238df10b26ec352da2f846a6fb5171
Author: Alex Vandiver <alexmv at bestpractical.com>
Date: Thu Dec 26 18:43:57 2013 -0500
Simplify wording; also, because on 4.2 and above we recommend Plugin()
diff --git a/lib/RT/Extension/Assets/Tutorial.pm b/lib/RT/Extension/Assets/Tutorial.pm
index 3cfd442..8441576 100644
--- a/lib/RT/Extension/Assets/Tutorial.pm
+++ b/lib/RT/Extension/Assets/Tutorial.pm
@@ -19,9 +19,9 @@ L<RT::Extension::Assets> distribution in the F<etc> directory. For
configuration, look in F<etc/Tutorial_Configuration.txt>. You can copy all or
part and paste it in your F<RT_SiteConfig.pm>.
-To load the test catalog, custom fields, and users, add
-C<RT::Extension::Assets> to your C<@Plugins> line after installing, then run
-the following from your RT directory:
+To load the test catalog, custom fields, and users, follow the
+installation instructions in L<RT::Extension::Assets/INSTALLATION>, then
+run the following from your RT directory:
sbin/rt-setup-database --action insert --datafile \
local/plugins/RT-Extension-Assets/etc/tutorialdata
commit 115ad65002a58e5d4a7cf9af289324675fa484bf
Author: Alex Vandiver <alexmv at bestpractical.com>
Date: Thu Dec 26 18:44:15 2013 -0500
Line up configuration lines
diff --git a/lib/RT/Extension/Assets/Tutorial.pm b/lib/RT/Extension/Assets/Tutorial.pm
index 8441576..36f57a1 100644
--- a/lib/RT/Extension/Assets/Tutorial.pm
+++ b/lib/RT/Extension/Assets/Tutorial.pm
@@ -182,9 +182,8 @@ F<RT_SiteConfig.pm>:
Set(%CustomFieldGroupings,
'RT::Asset' => {
- 'Asset Details' => ['Serial Number', 'Manufacturer', 'Type',
- 'Tracking Number'],
- 'Dates' => ['Support Expiration', 'Issue Date'],
+ 'Asset Details' => ['Serial Number', 'Manufacturer', 'Type', 'Tracking Number'],
+ 'Dates' => ['Support Expiration', 'Issue Date'],
},
);
commit 09c1100afdbf411f32ae308fd2cacd049496553d
Author: Alex Vandiver <alexmv at bestpractical.com>
Date: Thu Dec 26 18:45:56 2013 -0500
Minor wording changes
diff --git a/lib/RT/Extension/Assets/Tutorial.pm b/lib/RT/Extension/Assets/Tutorial.pm
index 36f57a1..83f1cb2 100644
--- a/lib/RT/Extension/Assets/Tutorial.pm
+++ b/lib/RT/Extension/Assets/Tutorial.pm
@@ -17,7 +17,7 @@ get a feel for all of the administrative controls. If you want to get a jump
start, the files to set up this basic configuration are provided in the
L<RT::Extension::Assets> distribution in the F<etc> directory. For
configuration, look in F<etc/Tutorial_Configuration.txt>. You can copy all or
-part and paste it in your F<RT_SiteConfig.pm>.
+part of it and paste it into your F<RT_SiteConfig.pm>.
To load the test catalog, custom fields, and users, follow the
installation instructions in L<RT::Extension::Assets/INSTALLATION>, then
@@ -30,7 +30,7 @@ This will change the default catalog name, create some users, and give those
users asset permissions. Only asset rights are granted, so you need to grant
additional rights if you want to experiment with creating tickets and linking
assets. The initial user passwords are 'password'. You should only run this on
-a test RT instance as it is not intended to be used for configuring a
+a test RT instance, as it is not intended to be used for configuring a
production system.
=head1 Getting Started
-----------------------------------------------------------------------
More information about the Bps-public-commit
mailing list