• 60
    • 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.

          Form Name

            [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.

            Hi there!

            From what I understood from your comments - in some organisations there is a strong need to have a very granular overview of actions happening within the Software Projects.
            I guess I could imagine that what you're looking for is something like Audit Log but laser-focused on a project related events; containing history of actions particularly interesting / crucial for project-oriented people (Scrum-masters, PMs, maybe Project Level Administrators?) more than for average Global Administrator, supervising the whole organisation's infrastructure.

            I am afraid we do not have any place that could collect and/or present such information reliably, easily and in a way that would not disturb nor build up noise for global administrators…

            But that sounds like a really valuable suggestion and I'll definitely try to spin the idea for further validation.

            Who knows - maybe we'll figure out something closer - in idea and execution - to PLA levelled, Project oriented Audit Log?
            I could guestimate that it's something within our reach but we have to validate the assumptions and run few explorations before I can give you any promises.

            ANYWAYS - that's definitely an interesting angle of approach.

            Thank you very much for the feedback!

            Best regards,
            Michal
            Sr. dev @ Jira Server TEAM

            🦊 Fox (Inactive) added a comment - Hi there! From what I understood from your comments - in some organisations there is a strong need to have a very granular overview of actions happening within the Software Projects. I guess I could imagine that what you're looking for is something like Audit Log but laser-focused on a project related events; containing history of actions particularly interesting / crucial for project-oriented people (Scrum-masters, PMs, maybe Project Level Administrators?) more than for average Global Administrator, supervising the whole organisation's infrastructure. I am afraid we do not have any place that could collect and/or present such information reliably, easily and in a way that would not disturb nor build up noise for global administrators… But that sounds like a really valuable suggestion and I'll definitely try to spin the idea for further validation. Who knows - maybe we'll figure out something closer - in idea and execution - to PLA levelled, Project oriented Audit Log? I could guestimate that it's something within our reach but we have to validate the assumptions and run few explorations before I can give you any promises. ANYWAYS - that's definitely an interesting angle of approach. Thank you very much for the feedback! Best regards, Michal Sr. dev @ Jira Server TEAM

            +1 for Simon's comment as pointed out by Rowan. https://jira.atlassian.com/browse/JSWSERVER-11871?focusedCommentId=968915&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-968915 I've had cases where people have been modifying the same sprint and I need to know who is the owner of that sprint so I can get the appropriate people to co-ordinate and also work on training. The person creating a sprint is often times a stakeholder in the process. I agree also that the person starting the sprint might also be useful information too, but not at the expense of the sprint creator. Is it possible to display both information?

            Vicki Lea Tsang added a comment - +1 for Simon's comment as pointed out by Rowan. https://jira.atlassian.com/browse/JSWSERVER-11871?focusedCommentId=968915&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-968915 I've had cases where people have been modifying the same sprint and I need to know who is the owner of that sprint so I can get the appropriate people to co-ordinate and also work on training. The person creating a sprint is often times a stakeholder in the process. I agree also that the person starting the sprint might also be useful information too, but not at the expense of the sprint creator. Is it possible to display both information?

            i guess me but ill go see im sure it was thanx to github
            \

            Megan Hoke added a comment - i guess me but ill go see im sure it was thanx to github \

            Won't the "sprint started" information be more beneficial here, tho? 
            Created but not started sprints are just containers within backlog and do not really interfere with the work nor workflow of the users…

            🦊 Fox (Inactive) added a comment - Won't the "sprint started" information be more beneficial here, tho?  Created but not started sprints are just containers within backlog and do not really interfere with the work nor workflow of the users…

            Rowan Kerr added a comment -

            Rowan Kerr added a comment - The comment from Simon above was a good summary of why this information would be helpful. https://jira.atlassian.com/browse/JSWSERVER-11871?focusedCommentId=968915&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-968915  

            HI!

            First of all - I'd like to thank you for reaching us and showing your expectations as to the behaviour of the application 

            For some time already we have been reviewing, rethinking and (re)working on Jira Software, focusing on transparency of user actions, user supervision  && data visibility. While scanning through all the feedback we received related to those areas I have found your request and believe I have few, hopefully good, pieces of information that could be of a hand for you. 

             

            When thinking about sprint creation per se - there is very little information connected with the fact WHOM actually created the sprint. 
            Sprint - on creation - is a de facto empty container with a "random"pre-defined name. 
            Could you elaborate on what kind of information would you be looking for here? What would be the questions you'd like to get the answers for and how would they influence your work?

            To be honest - keeping in mind that multiple users can create, re-arrange and delete multiple sprints just to fine-tune their (future) roadmap - I struggle to find any value in the information requested. But I'm guessing I just miss some information here.

             

            When it comes to getting to know who started or reopened the sprint - this information is not directly displayed anywhere in the system… yet.  

            But we realise it is crucial for the team members to be aware of what's going on with the sprint - who (and when) starts or re-opens one, hence it directly impacts their workflow. Therefore - we will add this information to the system.

            Moreover - the updates are already developed and are currently undergoing extensive tests. We also want to make them available as soon as possible - hopefully with next Jira Software Server release. 

             

            For consistency and better readability of the information you will be able to find them in a similar way as the (already available) information about "who closed sprint" action.

            We realise it might not be that obvious to find it - therefore we created a dedicated KB article that explains in details all the ways one can obtain such information. 

            The knowledge base article can be found here: https://confluence.atlassian.com/jirakb/checking-who-closed-a-sprint-947165301.html 

             

            Once we release the update extending the info about sprint start and re-open action - we'll also update the KB mentioned above so that you can find all the relevant guidance in one, simple article. 

             

            I hope these changes will help you to better understand what goes on within your teams!

             

            Best regards,
            Michal
            Sr. dev @ Jira Server TEAM

            🦊 Fox (Inactive) added a comment - HI! First of all - I'd like to thank you for reaching us and showing your expectations as to the behaviour of the application  For some time already we have been reviewing, rethinking and (re)working on Jira Software, focusing on transparency of user actions, user supervision  && data visibility. While scanning through all the feedback we received related to those areas I have found your request and believe I have few, hopefully good, pieces of information that could be of a hand for you.    When thinking about sprint creation per se - there is very little information connected with the fact WHOM actually created the sprint.  Sprint - on creation - is a de facto empty container with a "random"pre-defined name.  Could you elaborate on what kind of information would you be looking for here? What would be the questions you'd like to get the answers for and how would they influence your work? To be honest - keeping in mind that multiple users can create, re-arrange and delete multiple sprints just to fine-tune their (future) roadmap - I struggle to find any value in the information requested. But I'm guessing I just miss some information here.   When it comes to getting to know  who started  or  reopened  the sprint - this information is  not   directly displayed  anywhere in the system…  yet.    But we realise it is crucial for the team members to be aware of what's going on with the sprint - who (and when) starts or re-opens one, hence it directly impacts their workflow. Therefore - we will add this information to the system. Moreover - the updates are already developed and are currently undergoing extensive tests. We also want to make them available as soon as possible - hopefully with next Jira Software Server release.    For consistency and better readability of the information you will be able to find them in a similar way as the (already available) information about " who closed sprint " action. We realise it might not be that obvious to find it - therefore we created a dedicated KB article that explains in details all the ways one can obtain such information.  The knowledge base article can be found here:  https://confluence.atlassian.com/jirakb/checking-who-closed-a-sprint-947165301.html     Once we release the update extending the info about sprint start and re-open action - we'll also update the KB mentioned above so that you can find all the relevant guidance in one, simple article.    I hope these changes will help you to better understand what goes on within your teams!   Best regards, Michal Sr. dev @ Jira Server TEAM

            Would it also be possible to get this information for cloud also?

            Vicki Lea Tsang added a comment - Would it also be possible to get this information for cloud also?

            Magdalena added a comment -

            Hi All,

            Are there any news on that? When could we expect such information to be available? In which Jira'a version changes are expected?

            We are struggling with exactly the same problem as described above. I voted for issue. 
            I will be grateful for your response.

            Magda

            Magdalena added a comment - Hi All, Are there any news on that? When could we expect such information to be available? In which Jira'a version changes are expected? We are struggling with exactly the same problem as described above. I voted for issue.  I will be grateful for your response. Magda

            This is much needed information, starting, stoping, renaming, changing dates etc should all be written to the systems audit Log.

            Carl Blanchard added a comment - This is much needed information, starting, stoping, renaming, changing dates etc should all be written to the systems audit Log.

            Hey Subbu,

            I would like to follow-up on your comment. Query which I've share will show last access time for the Sprint and not who created the sprint.
            Please see example, both sprints were created by user admin:

            SELECT username,lastviewed,data FROM userhistoryitem WHERE data like '%Sprint%';
             username |  lastviewed   |   data
            ----------+---------------+----------
             admin    | 1480614263188 | Sprint 3
             admin    | 1480614263189 | Sprint 4
             test     | 1480614284592 | Sprint 3
             test     | 1480614284594 | Sprint 4
            

            Unfortunatly we don't have any details for user who create the sprint.

            One of possible workarounds is to track access logs:

            127.0.0.1 1127x655x1 admin [01/Dec/2016:18:47:01 +0100] "POST /rest/greenhopper/1.0/sprint/1 HTTP/1.1" 200 177 193 "http://127.0.0.1:8081/secure/RapidBoard.jspa?rapidView=1&view=planning&selectedIssue=AG-13" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:50.0) Gecko/20
            100101 Firefox/50.0" "18xlmez"
            

            and check the referer: RapidBoard.jspa?rapidView=1

            Andriy Yakovlev [Atlassian] added a comment - - edited Hey Subbu, I would like to follow-up on your comment. Query which I've share will show last access time for the Sprint and not who created the sprint. Please see example, both sprints were created by user admin: SELECT username,lastviewed,data FROM userhistoryitem WHERE data like '%Sprint%' ; username | lastviewed | data ----------+---------------+---------- admin | 1480614263188 | Sprint 3 admin | 1480614263189 | Sprint 4 test | 1480614284592 | Sprint 3 test | 1480614284594 | Sprint 4 Unfortunatly we don't have any details for user who create the sprint. One of possible workarounds is to track access logs: 127.0.0.1 1127x655x1 admin [01/Dec/2016:18:47:01 +0100] "POST / rest /greenhopper/1.0/sprint/1 HTTP/1.1" 200 177 193 "http: //127.0.0.1:8081/secure/RapidBoard.jspa?rapidView=1&view=planning&selectedIssue=AG-13" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:50.0) Gecko/20 100101 Firefox/50.0 " " 18xlmez" and check the referer: RapidBoard.jspa?rapidView=1

            I have voted for this request. This feature should be there in this application.

            Based on some search (credit goes to who posted the info and not myself!), I have found the following information that may be helpful (I have not verified it myself though).

            – How to find the creator of the Sprint in JIRA –

            SELECT username,lastviewed,data FROM userhistoryitem WHERE data = 'Name of Sprint';

            the 'lastviewed' entry gives the date/time the sprint was created in milliseconds and username reflects who created the sprint.


            thanks,
            Subbu

            Subbu Mahadevan added a comment - I have voted for this request. This feature should be there in this application. Based on some search (credit goes to who posted the info and not myself!), I have found the following information that may be helpful (I have not verified it myself though). – How to find the creator of the Sprint in JIRA – SELECT username,lastviewed,data FROM userhistoryitem WHERE data = 'Name of Sprint'; the 'lastviewed' entry gives the date/time the sprint was created in milliseconds and username reflects who created the sprint. thanks, Subbu

            Simon added a comment -

            This would be especially handy in my business. We have multiple sprints running within a project and a periodically have sprints created incorrectly.

            We have a very clear process but when the process is breached i can not hold anyone accountable nor can i provide any coaching unless the creator comes forward.

            I would actually prefer to have a "can create sprint" permission in my project, this would be more proactive solution.

            Simon added a comment - This would be especially handy in my business. We have multiple sprints running within a project and a periodically have sprints created incorrectly. We have a very clear process but when the process is breached i can not hold anyone accountable nor can i provide any coaching unless the creator comes forward. I would actually prefer to have a "can create sprint" permission in my project, this would be more proactive solution.

            I believe this basic functionality should be added ASAP.

            Senthil Palani added a comment - I believe this basic functionality should be added ASAP.

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

                Created:
                Updated: