When building a project, organizing information is one of the most important keys to have a Enjoyable Coding Flow experience. On jira, you can organize your documents that describe the application you wish to build on details, while maybe your documents are only pointers that refer to some feature that you wish to use on your application, but it will change the behavior when you define the rules or objectives of application when used by users.
You can have a feature that add some image. But uploading Images can have several purposes. The feature is being able to upload images for example, but the purpose can be, just to share them, or to sell them, or to rate them, or all at the same time, and those objectives, are what makes "your" application different from many others that have the same feature. They are able to upload images but that application have it's own purpose, just to save on the cloud, which will not be public and therefor there is no rate system and you cannot sell using that platform, etc..
Sometimes I feel that, not all developers like platforms like Jira, because Github or GibLab and many others code platforms with or without Web Interface, can do almost the same that Jira does, but for the perspective of a "Project Manager", can be useful to use Jira, since it looks cool and have "Tickets", which are some kind of forms that point to small pieces of the software that are part of application features development process.
Developing is really Hard, because you need to understand each feature, within many others that have similar purposes, but are using different approaches. [Poetic] -> but after you understand, if your logic mindset is ready to play with "solving challenges" which are problems you need to solve, you may find it super fun. My coding skills continue bad, because my Logic abilities are not so good and my experience on "writting code", is lower than my experience on writting texts with some logic behind, that doesn't need to respect Math. People some times say: "You don't need Math to code", but I believe that, if your mindset likes to work with Math, you will probably have less difficult to find a way to solve a problem.
My coding continues very Declarative while(if) the Math is not correct, I fail because I don't understand how "Computer Logic Work", which normally is based on Math, else Computers would be super funny tools like AI. I mean, AI is useful, but it makes mistakes like we do. I think AI could be very useful to control OpenSource in one single Perspective that is not about creating code or reviewing Code. AI could be super useful to control Applications usage, if you giving to AI, all details that AI needs to monitor to make better choices. This is My Own Allucination perspective, not from AI. :D
Imagine: AI have total control of your Machine, it knows all applications that can be used and have access to the documentation (which in Open Source is available for all), you can use Apache + MySQL + IPTables + SELinux and AI control Network and application Limits to maintain System performance and stability. Naturally this idea can be stupid in one other pespective. AI consume a lot of Machine resources, so at this point, AI is not useful at all, since the Machines controlled by AI, would need to duplicate their capacity to process information.
Anyway, to organize something really simple (as a conceptual idea), going through the Happy Path of dreaming how would work without thinking about the problems of the Unhappy Path, becomes a Monster of Documents and details like the WEB is, like the WORLD is, like LIFE is, and Jira works if developers are organized and if the client is as well organized and clear on the description of what the application needs to have, which takes some time to define, while AI can tell you what can fail, what the client is not seeing, what Laws cover those problems, how much cost they can have, what alternatives are available, etc... AI can help! Not for coding, like the last developer reviews point to, to describe how bad the new age of developers can become, if they assume that AI is better than human, when building some logic code, that needs to be reviewed by People. Even the Payed plans fail many times only by making questions that doesn't ask // code Logic but the thinking Logic, based on Knowledge, because by logic, everything is connected...
Anyway, you always need to give a "Direction", and in that aspect it works the same for all, natural or artificial intelligence. You need to define the best you can, what this application is able to do, what shouldn't do, what behavior happens if mistakes come up, and many other details that are not always directly to the subject but to the probability of unpredictability of user usage, that application development need to deal with. It is a strange event from a the client perspective, since you assume that developers can guide or suggest improvements, but they don't really see the common and basic issues that the application needs to have to "make sense". I mean, we go into the Purpose problem again. If the purpose is not correctly defined, the application have no use for any person. The purpose even to define some simple rule, need to exist, else nothing can be built. Nor for persons, nor for Machines.
Asking code to AI was likely more cool that I was expecting, for static sites. It is impressive, how easy a web site can change, by changing simple words that describe those changes. But I think that, AI can give awesome suggestions to help us to make choices, since in that aspect of sharing the results (at least in my objective perspective as a static web page) the results are impressive Good! I am sure that AI can code better than many, because like communication is complex, coding can be complex because you need to describe all the envirement details, to capture a good result. That last link site was made by AI. If don't give a objective to AI, AI don't even answer me :)
I don't know if normal "developer teams" have someone that is good to "translate" concepts on code while thinking deeper about each application they are going to build, but it looks like something that should exist more often. Firstly to explain it to developers and the ideas are not always easy to explain since you didn't spend time enought to think about them. So, at the end of this long blog post, I feel that, Building any application may ask us to learn a lot, only to define application functionality and purpose. But that is only the Happy Dream, which is good, since it represents the "Light" that the developers need to follow, to be able to detect issues, and guide the "Unhappy Path" to less errors or logicale mistakes, that don't need Math, but Knowledge...
If we read the documentation in a "objective" description, we may see that the objects are in a subjective state, since there is no direction to Guide the Code Flow and no code at all. Even then, each fragment that points into some direction, have some conditions that can be improved and many others that are not needed at all. When you create a Database Schema of those documents, you may need to review data context. I don't know why, but even if I like NoSQL databases Schemas, I like those "context rules" from SQL that describe "Tables Relationships". By using (JavaScript Objects Notation(JSON)) to organize data and represent it, is something I like. This is stupid because NoSQL don't need context relationships to work, while at the same time, it should be faster, if each "object" have the correct context data, that needs to print some specific results that are shouldn't be access from other table, with the results.