Comments
-
Ok, great, I wanted to check the filters to see if there was cleverness with sub-tasks, but your tasks are all parent level, so it's nothing to do with that. To simplify further, let's ignore the DOP board for now and concentrate on the ISB one. It was very useful for comparison and getting a good idea of what you've set…
-
I wish all my support type work read my "more information" questions and gave such clear answers! Your board config screenshot shows that you've got a simple, clear and pretty much ideal setup for the ISB Kanban board. But I get a bit lost when I get to the "HOWEVER" in the middle of the big paragraph. It's my reading, not…
-
It may be easier to split this into two parts. First, you talk about field configuration and issue types. This functionality is about field visibility and behaviour. It has nothing to do with boards (well, it can, in certain cases, but we'll come back to that) Secondly, the boards. You seem to be making changes and…
-
I think you're getting confused. If you re-read your original structure description, you've explicitly specified "Feature (Epic)" which means they're the same thing to you. So you'd use Epics for "features". If you want to go above Epics, there's a couple of layers - the usual one in Agile is a "Theme" which is a…
-
Ok, so you can create Epics, and use the boards to drag issues into Epics, or set the Epic link on them.Then add Portfolio to get the top layer, and you're done.
-
That *sounds* like you have Agile, but not Portfolio. I don't think I saw an Atlassian system at Summit that did not have Agile installed - you need to check that you have Agile first, then we can go from there.Portfolio is another story, you will need to add that too to get the overarching portfolio functionality
-
Ok, JIRA does Project / Issue / Sub-task itself. Epics would be considered at the same level as Stories.However, if you have the Agile addon, then you have Project / Epic / Issue / Sub taskThen for Portfolio, you need the Portfolio addon.
-
What do you mean by "heirarchy"?
-
Check what Alex said first, but there's one thing that trips up a lot of people (the UI design seems to fail a lot of users here, not sure why, when the rest of Confluence seems to work ok) When you go into "Edit and Share Filter", you'll see * the filter name * the "shared with" area * "add shares" <everyone> +Add * Save…
-
Think of the boards as a view of issues not a container or even an attribute of an issue. If you change an issue, you change data on it. Moving an issue from one column to another on board 1, it changes the status of an issue. So, on board 2, because it is just a View, it will also move columns (unless board 2's definition…
-
Yes, changing it to a numeric will fix the order. The other option is to prefix the shorter options with 00000
-
What type of field is MRR? I suspect it's not a number, so the issues are being sorted alphabetically, not numerically.
-
What task macro? That page doesn't mention it. What happens when you open the macro browser and type in "task"? And what are you expecting?
-
You'll need to write code to do that in JIRA.
-
Run a search for "custom-field is not empty"
-
Good good. If you wanted to use the post function, it was "update issue field", but the screen approach is usually better because it lets the user choose one...
-
You should have resolution on the "transition screen" that is on your "resolve and close" transition. Or set it with a psot-function that sets the resolution to a specific value. In both cases, have a look at your workflow to see what it is doing.
-
The issue sub-type is mostly a really useful construct here - your QA people can easily run filters for "QA stuff only", and your developers can ignore them :-) It also frees you up to have a different workflow and fields on QA items if you want. The only downside is remembering to create them...
-
I'd be strongly tempted to create a sub-task type of QA and then use the timetracking in there. It'll roll up to the main issue and remain independent of the development work.
-
I'm not sure what "no longer connected" might mean. Unable to log in? Can't reset the password? You probably need to talk to your admins, whatever the problem might be.
-
The answer you marked right already covers that.
-
You'll need to write a listener to catch the "issue updated" event on ticket A, make the decision to transition linked tickets, work out which issues need to be transitions and whether they have valid transitions and then "push" them. If you're using groovy, then you have the script runner and can probably use the "fast…
-
You're going to need to come up with a process that exports the user data from live Jira and pushes it into your test confluence database. You'll also need to configure the confluence system to use internal authentication (a one off), and then the SQL which will flip the flag in general settings after import (I'm not sure…
-
Ah, no, that's the point - if you don't have the user data in place, then the import of the backup will have problems, and certainly won't let you log in after it completes (assuming it completes at all)
-
Ok, good, I think you're right to ignore the 4.2 upgrade for now. Concentrate on the 2.10 import as whatever is going wrong in 4.2 is probably compounded by the fact you can't import to the same version. So, what does the log file say about the import? And your attemtps to log in afterwards?
-
What does the log file say at the point at which the import stalls? Also, your question isn't clear about whether you are taking a 2.10 backup and restoring it to a 2.10 system, or a 4.2 system. If it's 2.10 -> 4.2, I don't think that's going to work, you need to upgrade the data by going 2.10 -> 3.5 -> 4.2
-
Version reports like this rely on the data you put into a scrum board. If you're not using a scrum board, Jira won't be getting the information it needs to draw up the version report, so there's little point in having a report that won't show you much (Planning is only really done on Scrum boards). You can extract other…
-
Add versions to the project, and use them. See https://confluence.atlassian.com/display/JIRA/Managing+Versions If you're already using them, then it may be that another admin has shut off the project panel for some reason, but first, make sure you've got some issue with versions in the project!
-
I suspect Atlassian have looked at how people use Confluence and taken on board the common complaint that their products often send far too much email, and have simply decided to not implement something that will spam people even more.
-
I'm sorry, I was not very clear in my answer. My point is that watching is designed for the individuals - it lets a person choose what they want to watch.Most places that let people add watchers quickly find that the value disappears. I want to watch what I choose to watch. I don't want emails just because someone else…