Can't add a new Type value

I'm trying to add a new value in the Types bundle, but the only thing I can do is seeing the list of values and this message:

"This bundle is used in 7 projects and is default for 1 field. You should have admin permissions in all these projects to modify the bundle."

I am root, so I definitely have admin right. But just in case, I added root to the admin groups of all projects (the same field and same bundle is used among all projects).

So what should I do to add this new value?

Please help.
9 comments
Comment actions Permalink
That's weird, if the type is used in several projects, usually you can't change fundamental stuff like can be empty or default value.

Can you please provide a screenshot of what you see when you click on the Value Bundle name?
0
Comment actions Permalink
Sure.

As you can see, there are no options to add a new value.

Same is happening when I try to do the same in project settings (but I'd like to have it as a global setting).
Screen Shot 2014-06-10 at 15.56.05.png
0
Comment actions Permalink
Hi Andrea, Roman,

Please, check that under Administration> Projects you have no archived projects (enable 'Show archived projects' option). When the project is archived, bundles cannot be edited. Once you restore the project, the bundle can be changed.

Thank you.
0
Comment actions Permalink
Wow.

That's pretty hard to catch, isn't it?

I would almost define this as a bug, since YT doesn't tell that the bundle is used in some archived project: it just tell that I must be an admin (which I am).

By the way, thank you: this fixed the issue.
0
Comment actions Permalink
You are welcome!

Yes, completely agree. The truth is that it's UI issue and it's a bit hard to fix.
We'll change the message to the evident one instead of just 'you should have admin permissions in all projects'.

Thank you.
0
Comment actions Permalink
Unarchiving projects allows the bundles to be modified again. So I un-archive the old projects, then archive them back again.
0
Comment actions Permalink
Sorry, was not logged in and didn't see all the communication above when I logged in and replied.
0
Comment actions Permalink
I think it's not just the UI issue, it's more of a workflow issue. If a bundle is shared across several projects (States and Versions in our case), then it's never possible to have projects archived. We need to un-archive and archive back each time we add new versions to the bundle.
0
Comment actions Permalink
I agree with Michael - this makes it very difficult to make use of the archive feature at all. I had thought it could be possible to allow the conversion of a enumeration bundle to text bundle with the value set to that of the enumeration value... we'd loose the relationship to the issues with the bundle values, but at least we have it recorded within the ticket... Each time a project is going to be archived, the fields that are bundle values are converted to a text value. Another option would be to clone the bundle into Archived Bundle X and when an archive occurs it detects existing Archive bundles to re-associate all projects to. Finally, i thought about writing a utility that would use the  REST API to set a comment for each ticket that specifies the value of each field of bundle type at the time it is going to be archived. Then removes the field from the project. Again, this is not ideal...  any thoughts on a possible workaround? is there an issue reported in jetbrains YT for this ?
0

Please sign in to leave a comment.