Do Plugins

Jira plugin doesn't persist preferences correctly

Bug #354540 reported by Antoine Büsch on 2009-04-03

This bug affects 6 people

Affects		Status	Importance	Assigned to	Milestone
	Do Plugins	In Progress	Low	Chris S.
	gnome-do-plugins (Fedora)	Won't Fix	Undecided	redhat-bugs #894377

Bug Description

It seems that the Jira plugin doesn't persist its preferences correctly. Looking at the code, it looks like it tries to save the base URL and the list of projects in the preferences, but it loads them from GConf...

The attached patch seems to fix it for me.

Revision history for this message

Antoine Büsch (antoine-busch) wrote on 2009-04-03:

Patch to save the base URL and list of projects to GConf Edit (563 bytes, text/plain)

Revision history for this message

arbfranklin (arbfranklin-deactivatedaccount) wrote on 2009-05-28:

The patch looks good to me, is a project maintainer able to commit it to the mainline?

Revision history for this message

Chris S. (cszikszoy) wrote on 2009-07-10:

This should actually be fixed in a branch that I'm working on for Mono.Addins configuration extension points. I ended up rewriting all of Jira's preferences.

Changed in do-plugins:
assignee:	nobody → Chris S. (cszikszoy)
importance:	Undecided → Low
status:	New → In Progress

Revision history for this message

the_steiny (jason-steenstrapickens) wrote on 2010-05-06:

When can we expect to have this patch in a release? Seems a waste to have a perfectly good patch just sitting there doing nothing for almost a year when it could just be merged in.

Revision history for this message

Sandro (sandroid) wrote on 2011-03-30:

This one's been sitting around here stale for quite some time. I've created a bug under gnome-do-plugins package for ubuntu project referencing this bug and patch in the hopes it gets merged there at least. I suppose if Launchpad was built on Jira instead it would have been fixed years ago ;)

https://bugs.launchpad.net/ubuntu/+source/gnome-do-plugins/+bug/745704

-SM

Revision history for this message

In Red Hat Bugzilla #894377, Andrew (andrew-redhat-bugs) wrote on 2013-01-11:

Description of problem:
The Jira plugin for gnome-do will not save its configuration. If you go through the motions, exit the dialog and then bring it back up again, the fields you had filled in will be blank again

Version-Release number of selected component (if applicable):
gnome-do-plugins-0.8.4-12.fc18.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Start Do
2. Using the pulldown, navigate to the Jira plugin and hit configure
3. Fill in the settings, hit save and then bring up the configuration again

Actual results:
All the fields are blank

Expected results:
The configuration settings entered should be retained.

Additional info:
Also reported for Ubuntu
https://bugs.launchpad.net/do-plugins/+bug/354540

Revision history for this message

In Red Hat Bugzilla #894377, Theodore (theodore-redhat-bugs) wrote on 2013-01-11:

It would probably be best if we could get this fixed upstream, as they seem to have two different fixes pending. I'll see if I can't give the upstream bug a little nudge.

Revision history for this message

Theodore Lee (sharp-shiny) wrote on 2013-01-11:

Any progress on this bug? We've just had this reported in Fedora 18 so it seems to still be hanging around. Would the initial patch be the recommended fix if we were to patch this on the distro side, or should we perhaps cherry pick from the branch with the Jira preferences rewrite (assuming that's available)?

Revision history for this message

In Red Hat Bugzilla #894377, Fedora (fedora-redhat-bugs) wrote on 2013-12-21:

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Revision history for this message

In Red Hat Bugzilla #894377, Fedora (fedora-redhat-bugs) wrote on 2015-05-29:

#10

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 20 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Revision history for this message

In Red Hat Bugzilla #894377, Fedora (fedora-redhat-bugs) wrote on 2015-06-29:

#11

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Bug Watch Updater (bug-watch-updater) on 2017-10-28