# Update of Slicer issue tracker

**URL:** <https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437>\
**Category:** Development\
**Tags:** web-infrastructure\
**Created:** [June 2, 2017, 9:17pm UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437 "2017-06-02T21:17:49Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [June 2, 2017, 9:17pm UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437/1 "2017-06-02T21:17:49Z")

</div>

Hi Everyone,

Now that @freephile migrated the issue tracker to its new home:

> **[Issues · Slicer/Slicer](https://github.com/Slicer/Slicer/issues)**
>
> Multi-platform, free open source software for visualization and image computing. - Issues · Slicer/Slicer

(still available from [http://na-mic.org/Bug](http://na-mic.org/Bug) and [http://www.na-mic.org/Bug](http://www.na-mic.org/Bug) to ensure existing links work)

We are planning to upgrade the version of the tracker:

- You can get a feel for the interface here: [My View - MantisBT](https://www.mantisbt.org/bugs/my_view_page.php)

- You will find below a preview of the Slicer interface below.

- It will be a different user interface but we think that the new UI will improve the overall experience.

- The update also includes a lot of security fixes that are long overdue. See [Change Log - MantisBT](https://www.mantisbt.org/bugs/changelog_page.php)

**Note** In the future, we may also transition to using solely the GitHub issue tracker and project features but that will be discussed later.

 ![](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/1X/d63df6a8465acba173e66d3d63b0029bae0ddfb8.jpg)

---

<div class="post-metadata">

**Author:** ![ihnorton](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ihnorton/32/9_2.png) [@ihnorton](https://discourse.slicer.org/u/ihnorton)\
**Post date:** [June 3, 2017, 6:33pm UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437/2 "2017-06-03T18:33:29Z")

</div>

Thanks for this work. 💯 to moving to GitHub (or GitLab). It may be worth considering whether any more effort should be put in Mantis at all – except possibly to migrate content to GitHub (there are some scripts available which could be modified). Leaving the tracker frozen like the old Kitware trackers would also be fine. There is relatively minimal recent activity on the current tracker because of the reliability and email issues, lack of OAuth, etc., though the history is useful to keep.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [June 3, 2017, 6:55pm UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437/3 "2017-06-03T18:55:58Z")

</div>

Fully agree with moving issue tracking to GitHub.

GitHub’s issue tracker is still very basic, but it should be good enough to manage Slicer issues. When source code hosting will transition to GitHub then we’ll have to use GitHub’s issue tracker anyway (for managing pull requests, etc), so it would be simpler if we don’t need to manage two trackers. It’ll be also great to have integration with source code repository and not requiring separate account.

I think the simplest would be to prevent adding new issues to Mantis, but we should be able to update/close issues. When we closed or migrated all issues, we can make the repository read-only.

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [June 4, 2017, 2:22am UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437/4 "2017-06-04T02:22:27Z")

</div>

All for moving to GitHub for issue tracking!

Would be nice, but should not be a stopper, to time this with [migration of the source code to git](https://www.slicer.org/wiki/Documentation/Labs/TransitionToGit).

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [June 6, 2017, 9:00pm UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437/5 "2017-06-06T21:00:22Z")

</div>

To follow up, the Slicer issue tracker has been updated.

[https://issues.slicer.org](https://issues.slicer.org)

Make sure to `CTRL-F5` next time you visit the site.

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [June 8, 2017, 4:04am UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437/6 "2017-06-08T04:04:31Z")

</div>

While experimenting with the source integration plugin on Mantis, I re-triggered the import of the “correct” repository (Slicer/Slicer instead of jcfr/Slicer) and this took down the instance.

Waiting my mistake is addressed , the tracker is unavailable.

Cc: @freephile

---

<div class="post-metadata">

**Author:** ![freephile](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/freephile/32/248_2.png) [@freephile](https://discourse.slicer.org/u/freephile)\
**Post date:** [June 8, 2017, 4:48am UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437/7 "2017-06-08T04:48:19Z")

</div>

Actually, the tracker is available. The source integration plugin has a nasty feature whereby it blocks (queues) all requests by the same client behind the long-running “import” – making it appear that the server is hung. Meanwhile, any other client _can_ access the tracker and the load is miniscule.

@jcfr kill the import and/or use incognito mode and/or another browser. I can assure you that the server is fine.

---

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [October 29, 2018, 7:26pm UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437/8 "2018-10-29T19:26:50Z")

</div>

Bumping this thread since there’s already been some good conversation on this topic.

I have found it pretty difficult to use the search within the Mantis Tracker to find relevant results. It’s hard to quickly find if there is already an issue for a bug that I observe.

ITK recently moved from their issue tracker (JIRA) to GitHub issues. See this [post](https://discourse.itk.org/t/issues-in-github/1218/15) on their forum. Here is another [post](https://discourse.itk.org/t/github-issue-labels/1256) they had about using GitHub labels. For the most part I think Github Issues, Labels, and Milestones could replace a lot of primary functionality in the issue tracker. There isn’t default assigning of issues, but maybe some github apps could supplement any missing features.

---

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [October 29, 2018, 8:05pm UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437/9 "2018-10-29T20:05:27Z")

</div>

Also Github has issue templates which could encourage detailed steps to reproduce, platform, expected behavior, etc. which would be similar to the header fields on the Mantis Tracker. ITK is also using [github issue templates](https://help.github.com/articles/manually-creating-a-single-issue-template-for-your-repository/) to encourage users to provide details about bugs/features/etc. See [ITK Issue Template](https://github.com/InsightSoftwareConsortium/ITK/blob/master/ISSUE_TEMPLATE.md).

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [November 12, 2018, 7:51pm UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437/10 "2018-11-12T19:51:15Z")

</div>

Since mantis stores issues in a structured way (not just somewhat encouraging structure by offering a template), I find it much more efficient to locate issues in Mantis compared to GitHub.

However, I agree that probably GitHub’s issue tracker would be sufficient for Slicer, and definitely more accessible to users and developers, because most people are already familiar with GitHub, they don’t need to register yet another account, and the issue tracker integrates well with other GitHub features.

I think we should just first release Slicer-4.10.1, then move Slicer’s official repository to GitHub (still SVN is the official repository) and then switch to GitHub’s issue tracker.

@jcfr

---

<div class="post-metadata">

**Author:** ![phcerdan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/phcerdan/32/1559_2.png) [@phcerdan](https://discourse.slicer.org/u/phcerdan)\
**Post date:** [August 20, 2019, 12:37pm UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437/12 "2019-08-20T12:37:28Z")

</div>

Any ETA on enabling issues in github? Even if not official yet, would be nice to report bugs/issues there.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [August 20, 2019, 1:05pm UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437/13 "2019-08-20T13:05:55Z")

</div>

It would be nice to switch to github repository and issue tracker at the same time, to be able to leverage all the benefits of integration between github tools. However, there is no strict dependency, so we could start using github’s issue tracker for new issues any time.

@jcfr what is the planned date for switching to git?

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [August 20, 2019, 1:16pm UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437/14 "2019-08-20T13:16:28Z")

</div>

> [@lassoan](#):
>
> what is the planned date for switching to git?

This is the next major Slicer task on my list, we should expect the transition to happen in the next few weeks.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [August 21, 2019, 3:41pm UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437/15 "2019-08-21T15:41:49Z")

</div>

@phcerdan would this timeline work for you? Can you submit issues to [issues.slicer.org](http://issues.slicer.org)?

---

<div class="post-metadata">

**Author:** ![rprueckl](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/rprueckl/32/4240_2.png) [@rprueckl](https://discourse.slicer.org/u/rprueckl)\
**Post date:** [September 6, 2019, 8:39am UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437/16 "2019-09-06T08:39:17Z")

</div>

Yesterday, I tried to register to the bug tracking system without success, I didn’t get back an email that probably should have contained my password. Following the advice of @lassoan, I will post some issues I encountered in this thread.

---

<div class="post-metadata">

**Author:** ![rprueckl](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/rprueckl/32/4240_2.png) [@rprueckl](https://discourse.slicer.org/u/rprueckl)\
**Post date:** [September 6, 2019, 8:43am UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437/17 "2019-09-06T08:43:55Z")

</div>

Bug report  
Summary: Rulers that should be hidden are always visible after loading a scene  
Environment: 3DSlicer 4.10.2, Windows 10

Steps to reproduce:

- open slicer (standard layout)
- create a ruler somewhere
- hide it by clicking on the eye of the ruler in the Annotations module UI
- save the scene as mrb
- close scene (via file menu)
- load the mrb  
ruler is now visible in slice viewers, however the eye in the Annotations module UI is closed

---

<div class="post-metadata">

**Author:** ![rprueckl](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/rprueckl/32/4240_2.png) [@rprueckl](https://discourse.slicer.org/u/rprueckl)\
**Post date:** [September 6, 2019, 8:51am UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437/18 "2019-09-06T08:51:30Z")

</div>

Bug report  
Summary: Missing repeated question for saving scene when ending slicer  
Environment: 3DSlicer 4.10.2, Windows 10

Steps to reproduce:

- open slicer (standard layout)
- create a ruler somewhere (or make any other edit)
- click File --\> Exit
- the confirmation dialog appears --\> click ‘Cancel exit’
- click File --\> Exit  
program ends without any further question to save the scene

This code causes the immediate exit:

> <https://github.com/Slicer/Slicer/blob/45cf7d262fc07078fa94ece66520b0ac58f321d7/Base/QTApp/qSlicerMainWindow.cxx#L1104-L1111>

**(And another one in this post as I cannot post more than three consecutive posts):**

Bug report  
Summary: Broken marker placement cursor in non-standard layouts  
Environment: 3DSlicer 4.10.2, Windows 10

Steps to reproduce:

- open slicer (standard layout)
- switch to another layout (e.g. Compare --\> 2 viewers)
- click on the tool button to create a fiducial
- move cursor over the slice views  
the cursor does not change to the markup insertion cursor

this is caused by this code:

> <https://github.com/Slicer/Slicer/blob/45cf7d262fc07078fa94ece66520b0ac58f321d7/Base/QTGUI/qSlicerMouseModeToolBar.cxx#L538-L570>

–\> lines 544 and 561 should say `continue;`

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [September 6, 2019, 12:15pm UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437/19 "2019-09-06T12:15:17Z")

</div>

> [@rprueckl](#):
>
> Yesterday, I tried to register to the bug tracking system without success, I didn’t get back an email that probably should have contained my password

Hi -

I checked and your account exists on [issues.slicer.org](http://issues.slicer.org) under the email you used. I had it send a password reset link so let’s see if that works.

Anyway thanks for the reports. 👍 One question: have you tried the nightly builds? The markups have gotten a lot of improvements.

---

<div class="post-metadata">

**Author:** ![rprueckl](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/rprueckl/32/4240_2.png) [@rprueckl](https://discourse.slicer.org/u/rprueckl)\
**Post date:** [September 6, 2019, 12:20pm UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437/20 "2019-09-06T12:20:08Z")

</div>

I tried the issue with the ruler not being visible after loading a scene also with the nighlty build from 2019-08-29. It was the same there. Regarding the other two issues, the cited source code is unchanged to version 4.10.2 and I debugged those issues, so I assume they are still relevant.

So far no email received.  
Please remove my email address from your previous post - thanks!

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [September 6, 2019, 12:47pm UTC](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437/21 "2019-09-06T12:47:03Z")

</div>

> [@rprueckl](#):
>
> Please remove my email address from your previous post - thanks!

Sorry about that!

> [@rprueckl](#):
>
> So far no email received.

Not sure what’s up with that - I got the email that said your account was created. (I guess you checked your spam folder 😉).

Anyway looks like you’ve found some good fixes. The best way forward might be to put them in the form of a github pull request so people can easily test and comment.

Regarding the rulers they have always been a bit finicky and that’s why people have been moving functionality over to markups.

[Next page](https://discourse.slicer.org/t/update-of-slicer-issue-tracker/437.md?page=2)