Details
Improvement
Minor
Description
The path for piping configuration when editing a support department is not as reliable as piping it directly to pipe.php.
Update the path here to include pipe.php instead so that it looks something like:
/usr/bin/php /home/user/public_html/plugins/support_manager/pipe.php
Note that the path is dynamically generated, and should continue to be dynamically generated.
It would be a good idea also to update the tooltip. Currently it says:
Set your piping path as shown, but be sure to update it to point to where PHP is installed if it differs from what is shown.
Change this to:
Set your piping path as shown, but be sure to use the correct path to PHP on your server. Make sure pipe.php is executable. You may also need to edit pipe.php to include a hashbang on line 1 that would look something like: #!/usr/bin/php
Activity
Paul Phillips
created issue -
Paul Phillips
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Attachment | capture-for-jira-screenshot-20170627-133339-204.png [ 11638 ] |
Paul Phillips
made changes -
| Description |
The path for piping configuration when editing a support department is not as reliable as piping it directly to pipe.php. Update the path here to include pipe.php instead so that it looks something like: /usr/bin/php /home/user/public_html/plugins/support_manager/pipe.php Note that the path is dynamically generated, and should continue to be dynamically generated. It would be a good idea also to update the tooltip. Currently it says: *Set your piping path as shown, but be sure to update it to point to where PHP is installed if it differs from what is shown.* Change this to: *Set your piping path as shown, but be sure to use the correct path to PHP on your server. Make sure pipe.php is executable. You may also need to edit pipe.php to include a hashbang on line 1 that would look something like: #!/usr/bin/php" |
The path for piping configuration when editing a support department is not as reliable as piping it directly to pipe.php.
Update the path here to include pipe.php instead so that it looks something like: /usr/bin/php /home/user/public_html/plugins/support_manager/pipe.php Note that the path is dynamically generated, and should continue to be dynamically generated. It would be a good idea also to update the tooltip. Currently it says: *Set your piping path as shown, but be sure to update it to point to where PHP is installed if it differs from what is shown.* Change this to: *Set your piping path as shown, but be sure to use the correct path to PHP on your server. Make sure pipe.php is executable. You may also need to edit pipe.php to include a hashbang on line 1 that would look something like: #!/usr/bin/php"* |
Paul Phillips
made changes -
| Description |
The path for piping configuration when editing a support department is not as reliable as piping it directly to pipe.php.
Update the path here to include pipe.php instead so that it looks something like: /usr/bin/php /home/user/public_html/plugins/support_manager/pipe.php Note that the path is dynamically generated, and should continue to be dynamically generated. It would be a good idea also to update the tooltip. Currently it says: *Set your piping path as shown, but be sure to update it to point to where PHP is installed if it differs from what is shown.* Change this to: *Set your piping path as shown, but be sure to use the correct path to PHP on your server. Make sure pipe.php is executable. You may also need to edit pipe.php to include a hashbang on line 1 that would look something like: #!/usr/bin/php"* |
The path for piping configuration when editing a support department is not as reliable as piping it directly to pipe.php.
Update the path here to include pipe.php instead so that it looks something like: /usr/bin/php /home/user/public_html/plugins/support_manager/pipe.php Note that the path is dynamically generated, and should continue to be dynamically generated. It would be a good idea also to update the tooltip. Currently it says: *Set your piping path as shown, but be sure to update it to point to where PHP is installed if it differs from what is shown.* Change this to: *Set your piping path as shown, but be sure to use the correct path to PHP on your server. Make sure pipe.php is executable. You may also need to edit pipe.php to include a hashbang on line 1 that would look something like: #!/usr/bin/php* |
Tyson Phillips (Inactive)
made changes -
| Rank | Ranked higher |
Tyson Phillips (Inactive)
made changes -
| Story Points | 1 |
Tyson Phillips (Inactive)
made changes -
| Fix Version/s | 4.2.0-b1 [ 11014 ] | |
| Fix Version/s | Short Term [ 10800 ] |
Tyson Phillips (Inactive)
made changes -
| Sprint | 4.2.0 Sprint 1 [ 44 ] |
Tyson Phillips (Inactive)
made changes -
| Rank | Ranked lower |
Tyson Phillips (Inactive)
made changes -
| Sprint | 4.2.0 Sprint 1 [ 44 ] | 4.2.0 Sprint 2 [ 46 ] |
Tyson Phillips (Inactive)
made changes -
| Sprint | 4.2.0 Sprint 1 [ 46 ] | 4.2.0 Sprint 1, 4.2.0 Sprint 2 [ 46, 47 ] |
Tyson Phillips (Inactive)
made changes -
| Rank | Ranked higher |
Automated transition triggered when Jonathan Reissmueller created a branch in Stash -
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 54 minutes [ 3240 ] | |
| Worklog Id | 10335 [ 10335 ] |
Automated transition triggered when Jonathan Reissmueller created pull request #20 in Stash -
| Status | In Progress [ 3 ] | In Review [ 5 ] |
| Resolution | Fixed [ 1 ] |
Tyson Phillips (Inactive)
made changes -
| Sprint | 4.2.0 Sprint 1, 4.2.0 Sprint 2 [ 46, 47 ] | 4.2.0 Sprint 1, 4.2.0 Sprint 2, 4.2.0 Sprint 3 [ 46, 47, 48 ] |
Tyson Phillips (Inactive)
made changes -
| Rank | Ranked higher |
Automated transition triggered when Tyson Phillips (Inactive) merged pull request #20 in Stash -
| Status | In Review [ 5 ] | Closed [ 6 ] |
