We considered doing something like that briefly, but decided against it since it wouldn't be easy to get an organized list of the current requirements. With som

We considered doing something like that briefly, but decided against it since it wouldn't be easy to get an organized list of the current requirements. With some of our more zealous clients, business rules might have modifications every week. With that amount of changes going through, I could see Jira getting unwieldy. If you had to change a requirement, would you create a new one delete the old requirement or update the existing one? If there is a complex system with a couple hundred requirements, how would you organize them? Nested "folders" would be our ideal choice, but I think that we would just have to stick to some kind of label system in Jira. I don't think it's a bad idea, but for me it doesn't feel like the requirement is driving the project management. By convention it certainly could be, but I don't like having to rely on people following the convention.