Re: Obsolete configuration options

Damien Regad <[email protected]> Thu, 14 Sep 2023 18:23:59 +0200
Newsgroups gmane.comp.bug-tracking.mantis.general
Message-ID <CA+zp4VPqCXxktKJiM4FH-GndA8Zww9-7fGoAdSGfJ304rrBX2Q@mail.gmail.com>
--===============1867397853660573955==
Content-Type: multipart/alternative; boundary="00000000000024445a0605541b4c"

--00000000000024445a0605541b4c
Content-Type: text/plain; charset="UTF-8"

If you have a correctly setup and working Source Integration plugin, then
you should be all set.

For the record, the legacy source_* configs were already obsolete in 1.3.0
(see https://mantisbt.org/bugs/view.php?id=11732).

As for automatic resolution of issues, this is controlled by an option in
the Source Integration plugin's config (Resolve Fixed Issues). I think it
should work also when importing changesets initially, but to be honest I am
not really sure... I would have to look at the plugin's source code to
confirm, but don't have time for that at the moment. Also keep in mind that
the source integration plugin has 2 distinct regex, one for identifying
issues and one for resolving them.

On Thu, 14 Sept 2023 at 17:19, Fabian Cenedese <[email protected]> wrote:

> Hello
>
> After an update from 1.3.11 to current version (including current
> Source* plugins) I get some warnings in the admin/check page,
> probably because I just copied over the config files:
>
> The configuration option source_control_notes_view_status is now obsolete
> The configuration option source_control_account is now obsolete
> The configuration option source_control_set_status_to is now obsolete
> The configuration option source_control_regexp is now obsolete
> The configuration option source_control_fixed_regexp is now obsolete
> The configuration option status_percentage_legend is now obsolete
> The configuration option inline_file_exts is now obsolete
>
> Can these options just be removed? Or would the information need
> to be entered in some other place? I couldn't find information on
> https://github.com/mantisbt-plugins/source-integration/ (or other
> places).
>
> And a follow-up question: Should closing of issues with the #Fixed
> regexp just work with importing changesets? The commit messages
> are added to the mentioned issues but the issues are not closed
> (neither status nor resolution is changed). Is this related to the
> warnings above? Is it necessary to call ...?page=Source/checkin?
>
> Thanks
>
> bye  Fabi
>
>
>
> _______________________________________________
> mantisbt-help mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mantisbt-help
>

--00000000000024445a0605541b4c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">If you have a correctly setup and working Source Integrati=
on plugin, then you should be all set.<br><br>For the record, the legacy so=
urce_* configs were already obsolete in 1.3.0 (see<span class=3D"gmail-Appl=
e-converted-space">=C2=A0</span><a href=3D"https://mantisbt.org/bugs/view.p=
hp?id=3D11732" target=3D"_blank">https://mantisbt.org/bugs/view.php?id=3D11=
732</a>).<br><br>As for automatic resolution of issues, this is controlled =
by an option in the Source Integration plugin&#39;s config (Resolve Fixed I=
ssues). I think it should work also when importing changesets initially, bu=
t to be honest I am not really sure... I would have to look at the plugin&#=
39;s source code to confirm, but don&#39;t have time for that at the moment=
. Also keep in mind that the source integration plugin has 2 distinct regex=
, one for identifying issues and one for resolving them.<br></div><br><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, 14 Sept=
 2023 at 17:19, Fabian Cenedese &lt;<a href=3D"mailto:[email protected]">Ce=
[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:so=
lid;border-left-color:rgb(204,204,204);padding-left:1ex">Hello<br>
<br>
After an update from 1.3.11 to current version (including current<br>
Source* plugins) I get some warnings in the admin/check page,<br>
probably because I just copied over the config files:<br>
<br>
The configuration option source_control_notes_view_status is now obsolete<b=
r>
The configuration option source_control_account is now obsolete<br>
The configuration option source_control_set_status_to is now obsolete<br>
The configuration option source_control_regexp is now obsolete<br>
The configuration option source_control_fixed_regexp is now obsolete<br>
The configuration option status_percentage_legend is now obsolete<br>
The configuration option inline_file_exts is now obsolete<br>
<br>
Can these options just be removed? Or would the information need<br>
to be entered in some other place? I couldn&#39;t find information on<br>
<a href=3D"https://github.com/mantisbt-plugins/source-integration/" rel=3D"=
noreferrer" target=3D"_blank">https://github.com/mantisbt-plugins/source-in=
tegration/</a> (or other<br>
places).<br>
<br>
And a follow-up question: Should closing of issues with the #Fixed<br>
regexp just work with importing changesets? The commit messages<br>
are added to the mentioned issues but the issues are not closed<br>
(neither status nor resolution is changed). Is this related to the<br>
warnings above? Is it necessary to call ...?page=3DSource/checkin?<br>
<br>
Thanks<br>
<br>
bye=C2=A0 Fabi<br>
<br>
<br>
<br>
_______________________________________________<br>
mantisbt-help mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank">ma=
[email protected]</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/mantisbt-help" rel=
=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/listi=
nfo/mantisbt-help</a><br>
</blockquote></div>

--00000000000024445a0605541b4c--


--===============1867397853660573955==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============1867397853660573955==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
mantisbt-help mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mantisbt-help

--===============1867397853660573955==--