Comments
-
There's two ways you could be "linking Confluence to Jira" If you are doing it properly with Jira macros and shortcuts, then all you need to do is update the application link to use the new Jira url. If you're doing it with hard coded links (i.e. your users have entered the url as part of a link), then you will need to…
-
That sounds like design tasks are done outside the developers sprint. You could do them as sub-tasks, with the designers working on them outside the dev sprint and the devs ignoring them until that sub-task is closed. Or separate them completely, having their own issue type or even project, then your developers could…
-
No, I understood it perfectly. You are trying to add a "work description" field to a screen that is for updating issue data rather than the work log. As a work description is part of a work log and not the issue, this request is nonsense.
-
There's something wrong with your reverse proxy. We can't tell you anything more than that without seeing the analysis of response times, the checks on networking and hardware you've done, and how you've configured it (specifically, how you've done it differently to the recommendations)
-
You'd have to work hard as an admin to set up Jira to delete issues without human intervention. However, you say "board". You don't "delete" issues from a board - a board is a view of a set of issues, not a container. I suspect what you mean is that the board is no longer showing them. That would be caused simply by the…
-
The audit log captures the user id, date and key of an issue that is deleted. (It's in admin somewhere, use the admin search to look for "audit")
-
Which platform? There's quite a few you might mean here.
-
Which question do you want an answer to? Jira to Bitbucket or GitHub to Bitbucket?
-
Ok, it looks like you're doing roughly the right thing, but what are you actually asking for here?
-
You will need to find a field that displays the sub-tasks as part of their parent issue. Sub-tasks are normally not displayed on a backlog view and it doesn't make sense to try to rank them or put them into a sprint outside their parent; so even if you do show them in a backlog, there's nothing you can usefully do with…
-
The issue types must have the same field configuration and workflow. Then you can put the "issue type" field on the edit screen to allow drop-down changes.
-
You'll need some code to set it as a post-function, or some javascript hack or behaviour if you want to pre-populate it in the create screen. However, it is utterly pointless. The project key is in the issue's key already, and duplicating it in the summary just wastes space.
-
Define "broken". (And give context) It's not there. Clicks do nothing. It's "greyed out". It throws an error when you click. There's an angry penguin biting you every time you reach for the button. What is the actual problem?
-
Ok, so how are you measuring this? And what are the versions (before upgrade and after, although given the date of the post, I'd want to assume 7.12 is currently "latest")? Some of us would say "It feels slower" is not useful because it's not quantitative and humans are really very very bad at judging it, but I would still…
-
This is an old question, so there's now two answers in some cases: 1. You're not an admin on the right project (as before) 2. The project is an "Agility" project, which has no admin settings
-
Text fields are not countable, as their values are not bounded and listed. A statistics gadget would simply report 1 for each issue in the filter. So they're not much use in a statistics gadget. There are a couple of custom fields and searcher add-ons that try to do it, but they tend not to scale as well as encourage the…
-
Confluence is more aimed at free-form text and documentation, not entering "forms" or running process flows. Jira is more form-driven as it has custom fields and is based on a workflow engine. If you're going to to this in Confluence, you will need an add-on that provides forms. It's worth looking through the higher…
-
That's what I said, yes. I'm not sure what you think "combining the mentioned features" will do.
-
It depends very much on how you want to handle the non-development process you've got. You've said you want to take a sprint approach though, which instantly makes me want to say "Use the Scrum Software Development template". But I suspect you'll probably want to edit the workflow to match your desired process, and then…
-
Jira Software is an application that sits on top of Jira Core. So if you can do something in Core, you can do it in Software, as the whole of Core is there and working for you even before you look at Software functions.
-
Start at https://www.atlassian.com/agile
-
Do all five of your variables you are calculating from always have a value?
-
One thing you might check - run and save a filter for "project = xyz". Go to a dashboard and add a filter statistics gadget. Include resolved issues, select your filter and choose "status" for the statistic. This will confirm your list of status is complete, and give you a way to check the number of issues is correct.
-
Have you checked the permission checker?
-
Also, compare the histories for a disappearing issue and one that remains.
-
You can delete boards without touching the project, as I said. The issues on the copied board are the same underlying issues because the boards are selecting the same set. To change this, go to board admin and the main general config page where you can see and edit it.
-
If you get the same on Windows and Linux, then there is something wrong with your process or download, as I'd expect them to fail very differently.
-
This is why you should have very few admins and change control in place.
-
The query Alexey gave will show you sub-tasks assigned to you. My guesses as to why you might not see them are that * You are making the incorrect assumption that a sub-task inherits the assignee of the story * You are not using the built-in assignee field
-
You are mixing up projects with boards. A project contains a load of issues. If you delete the project, this will by necessity, delete the issues. A board is a view of a set of issues, not a container. You can delete a board and it won't affect the issues or the projects it was showing you. But going back to the original…