From: Jun Aruga <jaruga@redhat.com>
To: Ruby developers <ruby-core@ruby-lang.org>
Subject: [ruby-core:100322] Re: How to use backport custom field
Date: Wed, 7 Oct 2020 12:44:45 +0200 [thread overview]
Message-ID: <CAHE_3ChKMpA5TsDeV-HHNH2UyRHhdY0ppDFgbx615jCfcbTkJA@mail.gmail.com> (raw)
In-Reply-To: <CAK6HhsoQwQ0DDZDKV8Pk-Kizq=1BJnw1H1SWdyYamTTJoNpW2w@mail.gmail.com>
On Tue, Oct 6, 2020 at 7:25 PM NARUSE, Yui <naruse@airemix.jp> wrote:
>
> Thank you for confirmation.
> I checked again and to edit backport field it needs privilege.
> I think now you can edit it.
> thanks,
Thanks for the work. I confirmed the backport custom field UI now, and
I was able to use it.
As a reference for someone who is interested in this topic, I added 2
screen shot images after adding the privilege, to my reporting
repository [1].
You can see the backport custom field UI in the images.
* redmine_bugs_new_ticket_adding_privilege.png
* redmine_bugs_edit_ticket_adding_privilege.png
Could you add an explanation about the privilege needed to edit the
backport field to the wiki page [2]?
It's helpful for other people who are not sure about it.
Thank you.
[1] https://github.com/junaruga/report-ruby-backport-custom-field
[2] https://bugs.ruby-lang.org/projects/ruby/wiki/HowToRequestBackport
--
Jun | He - His - Him
next prev parent reply other threads:[~2020-10-07 10:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 14:30 [ruby-core:100309] How to use backport custom field Jun Aruga
2020-10-06 14:43 ` [ruby-core:100310] " NARUSE, Yui
2020-10-06 15:08 ` [ruby-core:100311] " Jun Aruga
2020-10-06 17:24 ` [ruby-core:100314] " NARUSE, Yui
2020-10-07 10:44 ` Jun Aruga [this message]
2020-10-07 11:41 ` [ruby-core:100326] " NARUSE, Yui
2020-10-07 12:56 ` [ruby-core:100327] " Jun Aruga
2020-10-07 13:15 ` [ruby-core:100328] " NARUSE, Yui
2020-10-07 13:30 ` [ruby-core:100330] " Jun Aruga
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHE_3ChKMpA5TsDeV-HHNH2UyRHhdY0ppDFgbx615jCfcbTkJA@mail.gmail.com \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).