More out of curiosity - Is there a technical reason that I should limit a custom field's context to projects / issues rather than just letting it exist against every issue type, and only using Screens to hide / show available fields against a project?
Does it chew up loads of extra memory or something? It's just an additional (complex) layer where things can go wrong when re-using custom field for a different project...
Just curious what business need prompted the capability.
Thanks!
I thought so. And considering the system can be reindexed, it's the kind of thing you can retrofit when performance actually becomes an issue?
Thanks Jason - confirmed a hunch.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.