Hi Kendall, they had been shown before the UI/UX changes, but it seems they got lost in the process, sorry for that. Could you open a ticket for this please? Thanks!

Nevermind, someone stumbled upon this already, see #906.

Cool, thanks for the quick respons(es).

I'm in the process of considering switching over to Chili rather than upgrading our Redmine (v1.1.2)

We use sub/parent tasks *very * extensively (sometimes 4-5 levels deep), so I think I need to explore the ramifications of this issue first.

It seems that the latest version I could upgrade to and still have links from a sub to a parent is v2.5?

If this is considered not such a big deal, am I missing some sort of workaround that would allow us to start right off with v3.0 while we're waiting for this issue to get fixed?

We do tend to be a bit conservative, so another consideration is - what is the last Chili version that would support switching a database back to (a more recent version of) RM with a minimum of drama?

TIA. . .

Hi Hans,

Hans Bangkok wrote:

It seems that the latest version I could upgrade to and still have links from a sub to a parent is v2.5?

If this is considered not such a big deal, am I missing some sort of workaround that would allow us to start right off with v3.0 while we're waiting for this issue to get fixed?

That's a bug/an omission in the new theme, I have working patch here I need to review before sending a pull request for it, but it should make it for 3.1.

We do tend to be a bit conservative, so another consideration is - what is the last Chili version that would support switching a database back to (a more recent version of) RM with a minimum of drama?

Everything other that 1.x will be impossible/hard to roll back, as the database format quite deeply changed in 2.0 and there's no downgrade path available for that that I know of.

Thanks a lot for those clarifications. However I'm still not clear on our immediate path forward.

If I go with the current 3.0 release, is this issue going to create a problem for us, or is there a workaround that makes this not really a problem? I only think this may be the case because the issue remained unnoticed for so many update cycles.

Failing that, then:

It seems that the latest version I could upgrade to and still have links from a sub to a parent is v2.5

Sorry, I realize this isn't technically a question - I'll try again.

Is the latest stable/released version I can upgrade to (from my old RM 1.1.2) where this isn't an issue v2.5?

Hans Bangkok wrote:

If I go with the current 3.0 release, is this issue going to create a problem for us, or is there a workaround that makes this not really a problem? I only think this may be the case because the issue remained unnoticed for so many update cycles.

Other than patching your installation by hand with the upcoming pull request, there is no way to show parent issues on the show issue view on 3.0.

It seems that the latest version I could upgrade to and still have links from a sub to a parent is v2.5

Sorry, I realize this isn't technically a question - I'll try again.

Is the latest stable/released version I can upgrade to (from my old RM 1.1.2) where this isn't an issue v2.5?

I'm sorry I wasn't clear enough :-) The new theme has been added in 3.0 and the parent issues not being shown is a problem introduced by the new theme, so any previous version shouldn't have this problem, I don't have an installation I can try this on lying around though.

Hi Felix,

Can I test your issue on my new testing 3.0 chiliproject system ?

Thanks

I'm no coder, but my understanding is that you don't need to ask Felix' permission. If you know how, just pull from his repository and Bob's your uncle.

If you don't know how, then some research and testing will be required to get up to speed, or just wait for 3.1 to be released.

The code is on github and free to use, see #906 for the corresponding issue.

I just pushed an upgraded version of the subtasks tree on the single issue view to also show the issue's parents, it should be included in 3.1 (which I had to push back to end of the month, sorry). If you want to test it, get the current master branch of the ChiliProject git repository.