Comments
-
ability to manage sprints is controlled by permissions - project > project settings > permissions - Manage sprints. if you want the "team leads" to be able to move stories then give them this permission.
-
I'm not sure I understand your inquiry here. JQL query will return a list of issues matching your query. The columns shown are defined by the columns you have chosen to display. The titles of the columns will be defined by the field names, you cannot change these. can you clarify what is going on?
-
@Stewart Meyer, I think we need more info here before we can effectively (?) respond. In Jira, w/ the exception of adding an approval state, the Assignee is the person that owns the issue and the workflow transitioning. Now, you could have a number of conditions tied to transition which restrict who can transition. Maybe…
-
you can certainly link the two but that doesn't do anything from a relationship perspective, i.e. like Epic > Story relationships. If the two 'epics' are actually associated w/ the same initiative then I would consider having a single initiative epic and then use Components to illustrate HTML and Dev. But hard to say what…
-
You can reach out to Atlassian Support and they can assist though changes are limited.
-
I would need more info to assist completely. What do you mean by move from company to company. do you want to move the project and issues from one cloud instance to another cloud instance? If so you could consider setting up the new projects in the new instance and then export all issues from the old and import into the…
-
@Pallavi Swamy, you can create the Kanban board and save to your profile location as mentioned above. Regarding Esther's comment "....only in your profile..." you can add the board shortcut to the JSD project sidebar using the "add shortcut". This allows anyone to access from the JSD project page, of course you need to…
-
trying to consume this but don't have all the info to do so effectively, i.e. priorities of issues and the sla rules itself. Can you share that info? I guess what you were not expecting are the last two issues (-65h and -72h) to be shown or are are some of the other issues not expected?
-
how are you defining a "Feature"? Is that an issuetype, label, custom field,...?
-
You should use the following considerations: * Maintain the designed relationship of Epic > Story > Sub-task * Setup your board to display by Epic * I recommend displaying the sub-tasks w/in the board but if you do not wish to do so then you can exclude them in the board's filter, i.e. include the following in your filter…
-
Other than the previous gadget, OOTB here are the available gadgets: * Sprint Health * Days Remaining * Sprint Burndown Beyond that I would check the marketplace
-
I had not seen that one before but really like it
-
and here is another - https://confluence.atlassian.com/jirasoftwarecloud/workflows-764478422.html
-
I think this is more of a discussion than question as there is really not "right" solution, just the one that works for you. I have used the following approaches: * Discuss w/ your team to come up w/ a "Bug Backlog Reduction Commitment", e.g. "reducing the bug backlog by 50% in 90d". Then create "Bug Reduction" stories for…
-
If this is reproducible please contactAtlassian Support. I have seen before and I have seen others report it. We need Atlassian to investigate when reproducible.
-
You can add from the Marketplace
-
Do you want them to have access to the application or just be a Customer. former - You can reactivate their license - Jira settings > user management find the user and reactivate later - Jira settings > user management find the user and reactivate, edit and remove access to Jira Software or other licenses as appropriate
-
There is a Rich Text gadget but that will require you to edit the text for each sprint.
-
Please go to Jira settings > user management > site management > site access and change to only user your team invites
-
You need a group or role defined first that includes the users you want to allow Browse access. For example: * Jira settings > user management > groups * add group * add members then you need to provide that group the necessary permission * project > project settings > permissions * edit the Browse permission and add the…
-
The most likely reason is that you are on a Business project and not a Software project. With BPs you cannot add a kanban/scrum board directly. Consider choosing your profile as the Location and then add a shortcut to your project sidebar.
-
I noted your additional details below (note for future reference consider editing the original post) and what I find strange is the fact that your issue has “no priority” initially. It is my understanding that issues will always have a priority when created. I am perplexed as to how you do not have a priority. Would you…
-
I don’t know of a way to do this with A4J. You might reach out to their support to see if it is possible.
-
You could consider a story with multiple sub-tasks. However unless your sprints are aligned and the assignees/teams are committed to it then the story could span multiple sprints.
-
Before I offer a solution let me provide an editorial. IMO, changing the priority baesd upon age is flawed. Priority should only change if indeed the priority of the issue changes. Rather, consider using ranking and manually order your backlog to reflect what is important to do is on. That said... you could set up a…
-
Please provide more info. Share your JQL and also as much info about the issue that is not showing as possible
-
You should see “Invite users” as below
-
very possible. I haven't use the addon for some time so I can't try it out. Have you use the search bar above to see if others have solved this previously?
-
There isn’t a way to automate this at least OOTB. What I have done is to create an excel template, export the users, drop them into my template and then filter on the ‘haven’t logged in since’. Copy the users and drop into an email.
-
You can change the sla goal filter to only include issue after the date you turn on the sla. Such as “createddate > 2020-01-01 and...