Comments
-
Ah, good. There's no burnup built in to the off-the-shelf system, but a few add-ons provide one.
-
The time tracking field appears on the list of fields you can add to a screen. "I would ask that you raise them as new questions though"
-
You'll need to edit all the text. The problem here is that the Jeditor add-on has stored a load of formatting information in a form of markup. JIRA has its own storage format for formatted text with the rich renderers, and doesn't understand the Jeditor format. All it can do is render what it sees as plain text as that.
-
That looks like an open sprint to me. Where's the header of the next sprint?
-
No, roles are there. Log in as an administrator, go to the admin cog at the top right next to your user profile picture and select any of the options. The admin screens all have a search at the top, into which you can type "roles", and you'll finf the admin screens for them there. Pressing g twice is another way to get to…
-
Sub-task estimates can be done, you just need to add the "time tracking" field to their screens. Or the points field. Two things to be aware of if you do this though. 1. Plain JIRA will add them up and display them on the parent issue, but they remain independent estimates. Let's say you have four issues, a parent logged…
-
The only ranking I've seen is the ranking in the JIRA Software application, aimed at boards, although it is usable in plain JIRA as well. It does not support your ranking-within-a-priority in a backlog, although you could get close by having a board that uses priority as swimlanes.
-
There's no real "export", as config items generally don't need exporting. As an admin though, just configure the field and read the list of there. As a non-admin, you could go into edit an issue that has the field and read the list that's embedded in the html for the page. Or stick a gadget on your dashboard. Filter…
-
When you say "completed", you mean you have put the end date on it and closed it? Could you give us a wider/longer screenshot, showing the headers of both sprints?
-
Not without coding - the component lead option is purely for components, and ignores issue type. What you could do with a little code (or an add-on) is have different workflows for the issue types and a post-function to do the assigning instead of using auto-assign.
-
It's not a button, it's a menu action under the "more" or "..." menu to the top-right of the issue. To configure the types, go to project administration and find the "issue type scheme". You need to make sure that there is at least one sub-task type in there.
-
Sorry, I'm being spectacularly unclear on this, so I'll try a different explanation You have an application that has webhooks which it triggers when certain things happen in it. One of these webhooks should post something into JIRA. The webhook needs to log into JIRA in order to do this, and for that it needs an account.…
-
No, you said you can't see a button for "splitting", and you're right, there isn't one. Because there's several ways to do it, with different descriptions. Creating sub-tasks is one way to split up a story. (Cloning and Create/edit are the other two obvious ones) You should find the "create subtask" under the actions menu…
-
I know you didn't ask, but your question was phrased in a way that suggested that you did not quite understand the permission schemes. The role you grant to the webhook should be the role that gives it the permissions it needs in the project, which is determined by the permission scheme. Imagine the webhook is a user. What…
-
Not quite, as I said, the story is a story. It is the starting point, but they're not neccessarily "the big part". They can be huge, they can be tiny. "I want to build a house from scratch" and "I want to hang a picture in my new house" are both stories, but they are of vastly different sizes. Epics are groups of stories…
-
How do you know the event is not being fired? Have you checked the notification scheme?
-
> I've currently got the Create Issues action as having JIRA Software application access, but this obviously also gives everyone permission to create issues. No, it doesn't. You've got a permission scheme that does that, but you don't have to, you can change it to grant whatever access you want >What permissions does a…
-
Move it to a JIRA on a Linux box first? Rename the project and directory, and amend the attachments table content, then re-do the export.
-
You should add users in the "admin -> users" section, put them in the right groups, then you'll be able to assign issues to them.
-
I think you are reading the documentation for Server Confluence, rather than Cloud, where you cannot do custom css.
-
The heirarchy is Epic (a huge tale), Story (a manageable tale), Task (a small piece of a story) A story is the starting point. They are often written in a way that tells a story about something a user might want, defining who the user is, what they want and why. They're often written by the users too, rather than…
-
You say "Confluence migration is done successfully", but then follow it with a load of stuff that is part of the migration. Did you check that Confluence was usable locally after you first started it? What do the log files say? Connection refused usually means your network is blocking something though. Can you reach…
-
Have a look at https://www.atlassian.com/software/bamboo
-
It's firing the event in my systems. Does your notification scheme have anyone set up to get notified on move?
-
It's a two-way street, I've learned a lot from the community!
-
The "share public" on the dashboard is there to do what it says - share the dashboard with everyone. If there are pieces of data on a shared dashboard that should not be public, then JIRA does the right thing, and hides them.If you want to share information with someone, you need to give them access to it.
-
JIRA is quite careful about the security of issues and tries to be consistent with a very simple rule - if you can't see the issue, you cannot see anything about it at all. It is dropped from reports, summaries, gadgets, search results, *everything*. This, of course, applies to your dashboards. If you want a user to see…
-
There's a bit more of a discussion on it over at https://community.atlassian.com/t5/Discussions/Why-bitbucket-team-changing-my-account-icon-to-rainbow/td-p/600167
-
And you got voted up a lot. I'm not going to claim I was the only person voting you up, but you deserved it.
-
Absolutely! The trick here is understanding what the resolution field is. I think Steven has helped you get there faster than I could. Just on the technical side though... Most of JIRA works on the principle that when the database entry for the resolution of an issue is empty, the issue is "unresolved" (and it displays…