최근 검색
최근 검색 없음
Yamile Martinez
가입한 날짜: 2021년 4월 15일
·
마지막 활동: 2021년 10월 27일
팔로잉
0
팔로워
0
총 활동 수
21
투표 수
0
플랜 수
12
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Yamile Martinez
Yamile Martinez님이 에 게시물을 만듦
We need a way to fix data after the ticket is closed if not Zendesk ticket data is no good for reporting and charting. All users are human and make mistakes, these are not caught before they are closed, therefore, we need a way to fix if we find that the tickets are reflecting something incorrectly. Currently, we cannot provide reporting to our customers because the data is reflecting wrong; this would entail for us to download to an Excel and manually manipulate the incorrect data.
This is not feasible; can we get something that will enable an Admin to fix Ticket Data already created and closed?
Even Jira allows you to edit after it has been closed and all other applications. We need this for at least the Admin Users to fix data
Thanks,
Yami
2020년 7월 23일에 게시됨 · Yamile Martinez
14
팔로워
10
투표 수
4
댓글
Yamile Martinez님이 에 댓글을 입력함
Hi,
I totally agree; we ended up changing the code and for us it works great:. In addition, we changed the dates to reflect the Month DD, YYYY HH:MM format.
Code changes are in the requests_page.hbs
{{breadcrumbs}}
{{#form 'requests_filter' class='request-table-toolbar'}}
{{input 'query' id='quick-search' type='search' class='requests-search'}}
{{label 'organization' for='request-organization-select' class='request-filter'}}
{{select 'organization' id='request-organization-select' class='request-filter'}}
{{subscribe}}
{{label 'status' for='request-status-select' class='request-filter'}}
{{select 'status' id='request-status-select' class='request-filter'}}
{{/form}}
{{#if query}}
{{else}}
{{#unless requests}}
{{t 'no_requests'}}
{{/unless}}
{{/if}}
{{#if requests}}
{{#isnt current_filter.identifier 'my'}}
{{/isnt}}
{{! FLX MOD: add Internal Priority, Type, Environment, Linked Ticket to the table }}
| Flx Priority | {{#link 'requests' sort_by='id'}}ID{{/link}} | {{t 'subject'}} | {{#link 'requests' sort_by='created_at'}}{{t 'created'}}{{/link}} | {{t 'requester'}} | {{#link 'requests' sort_by='status'}}{{t 'status'}}{{/link}} | Request Type | Environment | Bugzilla ID | Linked Ticket | Duplicate Ticket |
|---|
댓글 보기 · 2019년 9월 24일에 게시됨 · Yamile Martinez
0
팔로워
0
투표 수
0
댓글
Yamile Martinez님이 에 댓글을 입력함
Hi Kev,
Thanks for the confirmation,
I am still having the same error 401
"error": "Couldn't authenticate you"
I am not sure where to go from here?
| HTTP/1.1 401 Unauthorized | |
| Date | Tue, 09 Jul 2019 15:01:49 GMT |
| Content-Type | application/json; charset=UTF-8 |
| Content-Length | 37 |
| Connection | close |
| Set-Cookie | __cfduid=de597194bed2891a892a0a2b059df58151562684509; expires=Wed, 08-Jul-20 15:01:49 GMT; path=/; domain=.farelogixpartnersupport.zendesk.com; HttpOnly |
| WWW-Authenticate | Basic realm="Web Password" |
| Strict-Transport-Security | max-age=31536000; |
| Cache-Control | no-cache |
| X-Zendesk-Origin-Server | app59.pod13.usw2.zdsys.com |
| X-Request-Id | 4f3b2ce6a8a72a47-SEA |
| X-Runtime | 0.054535 |
| X-Zendesk-Request-Id | 53013f6df620e5fa7293 |
| Expect-CT | max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct" |
| Server | cloudflare |
| CF-RAY | 4f3b2ce6a8a72a47-SEA |
{
"error": "Couldn't authenticate you"
}
댓글 보기 · 2019년 7월 09일에 게시됨 · Yamile Martinez
0
팔로워
0
투표 수
0
댓글
Yamile Martinez님이 에 댓글을 입력함
Yamile Martinez님이 에 댓글을 입력함
I agree, this is a must-have in my eyes, since we must be able to provide at a glance all these custom fields that are applicable to your industry to provide the customer the detail to narrow down the time spent reviewing each ticket to see which one is the one they want to make a comment on.
Thanks,
Yami
댓글 보기 · 2019년 6월 20일에 게시됨 · Yamile Martinez
0
팔로워
0
투표 수
0
댓글