No, no. We were never intending to use any higher level category above epics. I simply changed the issue type of the old epics to umbrella to get them out of our way without deleting them (I wasn't sure how valuable they were to folks). Anyway, the old-style epics which are now umbrellas are deprecated at this point.

Confusion like yours is making me reconsider keeping them around at all...

Are we sticking with Epics now and not using the higher-level category (above epics) that was being discussed a few weeks ago?

Okay, thanks for the heads up! I am less concerned about this now that we have good epics. The "project" filters on the UXPROD Feature Kanban no longer user labels and are using the epics instead. Label as you wish

I tried to comment, but it got rejected by the system - hopefully this one will go through. For MARC import, we'll need a UI that expects to understand which MARC fields/subfields contain which data elements. For delimited, we'll need a UI more like in Excel, where the user need to define the delimitor character, and then how to parse the data into various data elements for various types of records. They are different enough that I think they'll need separate features.

Hi . Are these features labelled with batchimport conceptually distinct from the marcimport ones? Or are you wanting to change the label we use for this project? Thanks much!