You are currently working in version

Properties Wizard

Stage: of 12

How do you intend to use this IssueTracker? Choose which one you think is most appropriate.



Now enter the various sections that issues should be able to belong to.
It is recommended that you enter a few more than the default suggestions but these can be changed later.


Select the default section issues should belong to if someone who adds an issue do not specify which section it belongs to:

Ideally you select one but you can select multiple default sections by holding down the Ctrl key as you select sections.

Enter the kind of types and urgencies that issues should have.

Types Urgencies

Enter one item per line. All excessive whitespace will be removed.

If someone does not enter a type or an urgency what should be set by default.

Default type Default urgency

checked="checked"

 

checked="checked">

How should issues be sorted if not sorted by anything explicitly? By creation date or by modification date?

checked="checked" /> (Recommended) When sorted by creation date then posting of followups does not affect the default sort order in List Issues (or Complete List). This is similar to how Gmail sorts the inbox.

checked="checked" /> (Original) When sorted by modification date then old issues can appear at the top of the List Issues (or Complete list) even though added a long time ago. The modification date of the issue is the same as the creation date of the latest followup.

Are there people in your organization who might use these issue trackers a lot?
You can set up so called notifyables which simply maps a name to an email address and a group. Once these are set up you will be able to enter these people's names instead of having to remember their email address for settings and for the Tell-a-friend feature.

You can either define notifyables globally or locally. When defined globally (recommended) it will work for all inherent issue tracker instances. You can also define them locally which is useful if you want to contain everything in one single place.

(Tip! open these links in a new window and return here after)

You already have a global container for notifyables. /manage_GlobalManagementForm">Manage it here. Set up a global notifyables container in...

  • /manage_addProduct/IssueTrackerProduct/addNotifyableContainerForm?goto_after=1" >
    •

    You already have a few local notifyables set up here in this issue tracker.
    Manage them here. To set up local notifyables, follow this link.

    Are there people who should get an email notification on all added issues?
    Write the email addresses line by line or if you have defined notifyables you can just enter their name.


    Remember that you already have the following notifyables set up:

    ');"> (, )

    It seems that you have not set up any notifyables here. It is generally a useful thing to have because you can partly remember only the name and also if a notifyable person changes email address the name will still work as before.
    Do this, define local notifyables (names will only be defined then for this issuetracker) or create global notifyables container in which you can

    Who's running this issue tracker?

    The name is shown in email send-outs in the signature and the email is what the email comes from.

    Name:

    		 ">

    Email:

    		 "> The one you have now is invalid and this can cause problems with send-outs which are not followups.

    Some minor details about the display and submission of issues.

    File attachments

    Adding issues:

    		 " />

    Posting followups:

    		 " />

    Setting these to 0 switches the feature off.


    Date format:

    Use "clever" date display:

    checked="checked" id="sdc1" />   checked="checked" id="sdc0" />

    And now for some simple Yes/No questions.

    Should Managers be able to change attributes of an issue once submitted?

    checked="checked" id="allow1" />   checked="checked" id="allow0" />

    Should people be able use the Tell a friend widget?

    checked="checked" id="uses1" />   checked="checked" id="uses0" />

    Should people be able to subscribe to issues?

    checked="checked" id="allows1" />   checked="checked" id="allows0" />

    Should only the Manager be able to see the Statistics page?

    checked="checked" id="allowp1" />   checked="checked" id="allowp0" />

    Should email address be encoded to prevent spam-bots?

    checked="checked" id="allowe1" />   checked="checked" id="allowe0" />

    Show (if applicable) what people were notified when submitting an issue?

    checked="checked" id="allown1" />   checked="checked" id="allown0" />

    Show "Confidential issue" option?

    checked="checked" id="allowc1" />   checked="checked" id="allowc0" />

    Show "Hide me" option?

    checked="checked" id="allowh1" />   checked="checked" id="allowh0" />

    Show "URL" option?

    checked="checked" id="allowu1" />   checked="checked" id="allowu0" />

    Allow adding new sections

    checked="checked" id="allowns1" />   checked="checked" id="allowns0" />

    Use images in the menu

    checked="checked" id="allowim1" />   checked="checked" id="allowim0" />

    Finished!

    No, not quite actually. If you want to use Issue Assignment so issues can be assigned to Issue Tracker Users you will have to use the User Management management page.

    Other than that, you can now start using this issue tracker or review the Properties tab further.

    Complete Step out of 8

    Great! All properies set.

    To set more properties or change anything, visit the ">Properties again.
    Or
    Contents
    Or
    ">Start using " target="_blank">(in a new window)

    Lastly, some simple integer properties:

    How many issues do you want to display page batched page in List Issues?:

    How many files can be uploaded when you add an issue?:
    ...and for followups

    Do you want that Managers can change the attributes of an issue after it has been submitted:
    CHECKED>


    Sitemaster name:

    Sitemaster email:
    The one you have now is invalid and this can cause problems with notifcations when people don't want to reveal their own email addresses.

    Display dateformat:


    Now, let's set some simple string properties:

    Which HTML colour do you want to use for Odd (1,3,5...) rows in List Issues?

    Which HTML colour do you want to use for Even (2,4,6...) rows in List Issues?

    Do you want to stick a prefix to the id of issue objects, if not leave empty?
    E.g. /mytracker/admin-0007 instead of just /mytracker/0007


    Are there people who should get an email notification on all added issues?

    Remember that you already have the following notifyables set up:

     (, )

    Should people be able to subscribe to issues?
    CHECKED>

    Should only the Manager be able to see the Statistics page?
    CHECKED>


    Now, select which ones of these are default ones:

    Default type Default urgency

    Now enter the types and urgencies you want that issues can have:

    Types Urgencies

    Which one (or which ones) of these do you want to be default. I.e. chosen if none is chosen when an issue is added:


    Please enter what various Sections you want to employ: