• 44
    • 18
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      It would be useful to store in the database the creator of the sprints. When we have several different sprints with the same name, it would be a useful information to distinguish those sprints.

            [JSWSERVER-11871] As a user, I'd like to know who is the sprints creator

            Since Jira contains the AO_60DB71_AUDITENTRY table in the database where the OPEN and CLOSE operations are already stored, it can't be rocket science to track the creation an changes as well.
            Since the deletion of sprints is already saved in the System AUDIT LOG, it would be particularly nice if the creation or modification could also be found there.

            But I'm afraid since both the reporter and the assignee of this task are inactive, the sugesstion goes to Santa Claus

            Hannes Medwed added a comment - Since Jira contains the AO_60DB71_AUDITENTRY table in the database where the OPEN and CLOSE operations are already stored, it can't be rocket science to track the creation an changes as well. Since the deletion of sprints is already saved in the System AUDIT LOG, it would be particularly nice if the creation or modification could also be found there. But I'm afraid since both the reporter and the assignee of this task are inactive, the sugesstion goes to Santa Claus

            These are all very basic, should be part of your core functionality. It's been more than 5 years. please do fix it asap.

            ajjaiah_nagarajappa added a comment - These are all very basic, should be part of your core functionality. It's been more than 5 years. please do fix it asap.

            raj kumar added a comment -

            This issue is required and helps to understand who has created the Sprints especially when there is a change of Scrum masters from one team to another. Would recommend to fix it.

            Regards

            Raj Kumar 

            raj kumar added a comment - This issue is required and helps to understand who has created the Sprints especially when there is a change of Scrum masters from one team to another. Would recommend to fix it. Regards Raj Kumar 

            Also, this issue has been open for 6 years. Why has a decision not been made?

            Steven Tucker added a comment - Also, this issue has been open for 6 years. Why has a decision not been made?

            +1
            We have sprints created by a team member other than the BA or SM and this would be very helpful to know.

            Steven Tucker added a comment - +1 We have sprints created by a team member other than the BA or SM and this would be very helpful to know.

            Dear @Atlassian Team,

            What is the problem in adding this info in audit Log? It's very basic and important data in the agile world.

            Balavinayagamoorthi Ramasamy added a comment - Dear @Atlassian Team, What is the problem in adding this info in audit Log? It's very basic and important data in the agile world.

            I am having similar issues,  please help with fixing this issue 

            Shola Freeman added a comment - I am having similar issues,  please help with fixing this issue 

            Useful info, please address

            Susan McCasland added a comment - Useful info, please address

            Ditto, exactly same problem here. Please fix this!

             

            Janne Kiiskilä added a comment - Ditto, exactly same problem here. Please fix this!  

            Agree with Simon's comments this will be useful. I've additional had similar issues as illustrated on this link:

            https://community.atlassian.com/t5/Jira-Software-questions/Sprint-appears-to-be-owned-by-a-different-board-from-the-one/qaq-p/200963

            Sprints inadvertently appearing on multiple teams boards and being renamed and worked on by multiple teams is difficult to fix when you don't know who's sprint it technically was in the first place.

             

            An "About" or "Sprint" info on the 3 dots option for a sprint for details which is prior to sprint start (as you can find that info in the reports) would be useful to get to a root cause in these situations nothing major:

            • Sprint Created by [Username] on date XYZ
            • Sprint Renamed by [Username] on date XYZ

            a log of both of those would solve the issues I've been encountering with sprints.

            Lewis Cook added a comment - Agree with Simon's comments this will be useful. I've additional had similar issues as illustrated on this link: https://community.atlassian.com/t5/Jira-Software-questions/Sprint-appears-to-be-owned-by-a-different-board-from-the-one/qaq-p/200963 Sprints inadvertently appearing on multiple teams boards and being renamed and worked on by multiple teams is difficult to fix when you don't know who's sprint it technically was in the first place.   An "About" or "Sprint" info on the 3 dots option for a sprint for details which is prior to sprint start (as you can find that info in the reports) would be useful to get to a root cause in these situations nothing major: Sprint Created by [Username] on date XYZ Sprint Renamed by [Username]  on date XYZ a log of both of those would solve the issues I've been encountering with sprints.

              mdyro 🦊 Fox (Inactive)
              cgauterio Clarissa Gauterio (Inactive)
              Votes:
              219 Vote for this issue
              Watchers:
              134 Start watching this issue

                Created:
                Updated: