最近の検索
最近の検索はありません

Nick Vincent-Maloney
参加日2021年4月15日
·
前回のアクティビティ2023年9月22日
フォロー中
0
フォロワー
0
合計アクティビティ
32
投票
6
受信登録
13
アクティビティの概要
バッジ
記事
投稿
コミュニティへのコメント
記事へのコメント
アクティビティの概要
さんの最近のアクティビティ Nick Vincent-Maloney
Nick Vincent-Maloneyさんがコメントを作成しました:
Too bad you guys broke markdown... the new internal note editor is horrible. We use complex macros to auto-populate internal notes with tons of markdown and now all that is broken. Jira does this too and they suck at it. One rule of thumb over all my years of using markdown, DO NOT RENDER IT ON THE FLY. It makes it extremely buggy and hard to edit while working on crafting a message. Bring back the preview function, PLEASE!!!
コメントを表示 · 投稿日時:2023年9月22日 · Nick Vincent-Maloney
0
フォロワー
1
投票
0
コメント
Nick Vincent-Maloneyさんがコメントを作成しました:
Too bad you guys broke markdown... the new internal note editor is horrible. We use complex macros to auto-populate internal notes with tons of markdown and now all that is broken. Jira does this too and they suck at it. One rule of thumb over all my years of using markdown, DO NOT RENDER IT ON THE FLY. It makes it extremely buggy and hard to edit while working on crafting a message. Bring back the preview function, PLEASE!!!
コメントを表示 · 投稿日時:2023年9月06日 · Nick Vincent-Maloney
0
フォロワー
0
投票
0
コメント
Nick Vincent-Maloneyさんがコメントを作成しました:
It's almost as if ZD didn't even think this through with proper testing and UI/UX specialists. How is that possible? Well, I say it's that ZD has lost sight of its core values. When I started using ZD over 8 years ago, I felt liked they cared about me and my use-cases. Nowadays, no luck... I'm just another subscription they milk for profits.
コメントを表示 · 投稿日時:2022年8月23日 · Nick Vincent-Maloney
0
フォロワー
4
投票
0
コメント
Nick Vincent-Maloneyさんがコメントを作成しました:
Agreed Matthias Miltenberger! Another bonehead move on ZD's part. We already struggle with this silly feature in Jira. MD is such a powerful tool and both these companies are ruining in a failed attempt to make it more user-friendly.
コメントを表示 · 投稿日時:2022年4月28日 · Nick Vincent-Maloney
0
フォロワー
1
投票
0
コメント
Nick Vincent-Maloneyさんがコメントを作成しました:
I am always flabbergasted at the inane changes ZD seems to make despite all these comments and concerns. Changing to the requester in the ticket tab is utterly silly and I just can't imagine why ZD would do that. I agree with Ethan, can someone at ZD share the process by which this change was made? Was it user feedback? I sure as heck didn't ask for this.If such a change is made, maintaining a way to change it back seems so obvious.
In fact, almost every change I do ask for is never implemented and all the huge changes that are made, I never asked for. I guess our use cases are just wonky compared to everyone else???
コメントを表示 · 編集日時:2022年4月27日 · Nick Vincent-Maloney
0
フォロワー
12
投票
0
コメント
Nick Vincent-Maloneyさんがコメントを作成しました:
This is a great example of ZD getting locked into their original core technology without thinking about their actual users as they grew bigger and bigger. We've been using ZD for many years (something like 8 or so), and I've been repeatedly disappointed by their slow migration towards being a huge, uncaring company. I feel like I'm not listened to anymore and their weird little design flaws are super annoying. We've had to hack and compromise quite a lot (in system configuration and our own app design) just to make this whole system work for us. This email thing is a big one that we struggle with constantly. The idea that users have a "primary" email address is absolutely ridiculous. Come on ZD, get with the program.
コメントを表示 · 投稿日時:2021年12月15日 · Nick Vincent-Maloney
0
フォロワー
8
投票
0
コメント
Nick Vincent-Maloneyさんが投稿を作成しました:
IMO, the fact that ZD doesn't have better URL support is somewhat shocking. Here are some examples of what I mean:
1. They don't support reasonable and sensible URLs (only weird IDs with broken slugs)
2. They don't support 404s when articles are archived or removed
3. They have limited support for articles that are renamed, such that only if the ID is present will it redirect
4. There are bugs in the URL mechanism that I've reported to ZD that still exist (weird character issues, dangling hyphens, no support for certain important and valid URL characters)
I'd really like to see some of these important issues resolved. How about you?
投稿日時:2021年4月19日 · Nick Vincent-Maloney
0
フォロワー
1
投票
0
コメント
Nick Vincent-Maloneyさんがコメントを作成しました:
0
フォロワー
1
投票
0
コメント
Nick Vincent-Maloneyさんがコメントを作成しました:
One thing I've done in the months since posting this is to take advantage or redirects on our domain. I manage the server that hosts the website so this is trivial to do. For example:
Redirect 302 /articles/product-support-123 https://help.domain.com/hc/en-us/articles/360046759191-Product-Support-123
Then when you visit...
http://www.domain.com/articles/product-support-123
you are redirected to...
https://help.domain.com/hc/en-us/articles/362346759444-Product-Support-123
I've gathered up a hefty lists of redirects in my HTACCESS file (Apache per folder config). You can also do this in the virtual hosts file if you have access to it.
コメントを表示 · 投稿日時:2020年10月15日 · Nick Vincent-Maloney
0
フォロワー
0
投票
0
コメント
Nick Vincent-Maloneyさんがコメントを作成しました:
I wanted to do something similar... I have several "forms" that will create different types of tickets, and I want to auto-fill each subject and maybe description with text... So I did something like the below. Note that I used web developer options in Chrome or Firefox to find the dropdown ID, "request_issue_type_select".
If this seems wrong or if anyone thinks it'll cause problems, please let me know.
// Set the value of the selected dropdown option to a variable
var $request_type = $('#request_issue_type_select option:selected').text();
// Test for option you want, eg, you would have one of these for each form
// you have that you want to auto-fill
if ($request_type == 'Virtual Brunch Sign Up') {
$('#request_subject').val('Virtual Brunch Sign Up');
}
// Conditionally hide description while setting the subject text
if ($request_type == 'Virtual Brunch Sign Up') {
$('#request_subject').val('Virtual Brunch Sign Up'); // Autofill subject
$('.form-field.request_description').hide(); // Hide description
}
コメントを表示 · 投稿日時:2020年9月16日 · Nick Vincent-Maloney
0
フォロワー
0
投票
0
コメント