Changes between Version 37 and Version 38 of TicketToSalesforcePlugin


Ignore:
Timestamp:
Oct 13, 2016, 6:52:11 PM (8 years ago)
Author:
figaro
Comment:

Moved example to functional description

Legend:

Unmodified
Added
Removed
Modified

  • TicketToSalesforcePlugin

    v37 v38  
    55== Description
    66
    7 This plugin synchronizes Trac tickets in [http://www.salesforce.com Salesforce]: Trac tickets are reflected by the Salesforce custom objects, Ticket and Comment. Ticket objects are linked to Cases via many-to-many relationship provided by the !CaseTicketLink custom object. Even though this is a many-to-many relation, Trac uses a custom text field for the Case number, so it's essentially many-to-one. 
     7This plugin synchronizes Trac tickets in [http://www.salesforce.com Salesforce]: Trac tickets are reflected by the Salesforce custom objects, Ticket and Comment. Ticket objects are linked to Cases via many-to-many relationship provided by the !CaseTicketLink custom object. Even though this is a many-to-many relation, Trac uses a custom text field for the Case number, so it's essentially many-to-one.
    88
    99Comment objects are related to Ticket objects via the link custom object, !TicketCommentLink. The related lists layouts are modified to display the related object fields rather then the object id.
    … …  
    3030}}}
    3131
     32=== Ticket view
     33
     34[[Image(ticket_view.png, border=2)]]
     35
     36=== Case view
     37
     38[[Image(case_view.png, border=2)]]
     39
    3240== Bugs/Feature Requests
    3341
    … …  
    3947
    4048[[TicketQuery(component=TicketToSalesforcePlugin&group=type,format=progress)]]
     49
     50=== Known Issues
     51
     52 * Even though the case number is numerical, you must enter it with whatever leading zeros are configured in Salesforce for this field, since the query treats this as a string.
     53 * This plugin comes with a `TicketValidator` which checks if the entered case number actually exists in Saleforce, but also if case number is blank. So if you are using the [wiki:TicketValidatorPlugin] you will !get two warning messages, "case number required" upon attempting to submit a ticket without a case number.
    4154
    4255== Download
    … …  
    5770General instructions on installing Trac plugins can be found on the [TracPlugins#InstallingaTracplugin TracPlugins] page.
    5871
    59 == Example
     72== Configuration
    6073
    6174Example settings in `trac.ini` are:
    … …  
    8194}}}
    8295
    83 == Known Issues
    84 
    85  * Even though the case number is numerical, you must enter it with whatever leading zeros are configured in Salesforce for this field, since the query treats this as a string.
    86  * This plugin comes with a `TicketValidator` which checks if the entered case number actually exists in Saleforce, but also if case number is blank - so if you are using the [wiki:TicketValidatorPlugin] you will !get two warning messages, "case number required" upon attempting to submit a ticket without a case number.
    87 
    88 == Screen Shots
    89 
    90 === Ticket view
    91 
    92 [[Image(ticket_view.png)]]
    93 
    94 === Case view
    95 
    96 [[Image(case_view.png)]]
    97 
    9896== Recent Changes
    9997