Comments
-
Yes, as long as your "task" issue type is at the same level as Story in the Epic -> Story -> Sub-task hierarchy. i.e it is Epic -> Tasjk -> Sub-task
-
You need to explain what this has to do with Atlassian. I've removed the link from your question in case this is spam.
-
There's no image, and I can't work out what you want from the description. Could you explain it better and/or give us the image?
-
I can't pick 3, it varies far too much by mood and the last time I heard it. But to pick the ones that cover a lot of moods and have short repeat cycles: Night on a Bare Mountain (Mussorgsky) Dominion (Sisters) Journey of the Sorcerer (The Eagles)
-
The thing they added to 7.4 was indeed a line in the permissions scheme.
-
Does the user running it have the right to create issues in the project? I suspect it's more likely to be content though. Does the project include the right sub-task type? Can you create a sub-task manually? Are there validators or mandatory fields your post-functions don't take into account?
-
If you run a search for "labels = RPA-2017", does it return issues only in one project?
-
Project in (x, y, z) and issuetype = Epic is neater than chains of OR junctions. Or even, assuming you are using project categories, Category = <something> and issuetype = Epic
-
No, you can't. The point of hiding the page completely is that, well, the user can't see it. You don't want the page information leaking out into search results and then giving people a link to a page they can't actually access. That's a terrible experience for them, frustrating and annoying.
-
Can you connect with that?
-
Ah, I misunderstood the direction! What you'll need to do is edit the "issue type scheme" for your project, adding in the other types you need. Then amend the workflow scheme to say "use these workflows for those issue types" You can do it either way around - the workflow scheme is just a mapping - it lists all possible…
-
They do actively check this stuff and alert us. Solution Partners usually get an earlier mention if they are starting to think they might be affected.
-
You can use the "local" settings in the pg_hba.conf if you're on the same server.
-
7.3 allows for some workflow changes 7.4 adds a flag so your admins can stop your project leads making a mess with it 7.5 adds the ability to modify the screens So, you'll need to upgrade to get some of those functions
-
Yes, there's a couple of bug fixes and tweaks. What are you looking for?
-
The incoming mail is too divorced from outgoing for it to know. Outgoing mail is done by "send mail to the address associated with this user", it has nothing to do with the incoming mail. What you need to do is capture the difference between (say) Soley@internal.mail.address and Soley@external.mail.address and route them…
-
What instructions are you following? Agile became Software in Jira 7, so wordings have changed quite a lot, and it sounds like you might be looking at old docs.
-
I would use ScriptRunner to write a post-function that would populate a select list with your criteria (resolution time in text rather than numbers), based on the calculation made at the time the issue moves to resolved/closed/etc. Then, you can use that in a pie chart gadget to count the issues in each band.
-
Yes. In the space permissions, make sure only your specific users have "use space" permission. Remove all the other users and groups.
-
Right, so create issues as normal. Then build reports based on "sprint is empty" to find issues that did not go into a sprint.
-
Service Desk only supports using a Confluence Space as a knowledge base. You might be able to write add-ons that mimic similar capabilities with other systems, but I've not seen anyone do that yet.
-
This is a question for a Swift forum really. We're Atlassian users and developers, not Swift coders. Your code is failing to build because of something you've done wrong in Swift. Yes, I know you're using Jira mobile connect, and we'd be able to help if the errors were there, but your code is not even starting to look at…
-
Does your admin account have access to Jira Software? Check it's in the group that allows you into Software.
-
It sounds like your add-on is not using the base url it should be reading from the system config (or, if it is, then the base url in the settings has not been changed to https)
-
You need to start by reading the logs to see what is going wrong.
-
No. Issues removed from a sprint are issues you have in the sprint when you start it, but decide to remove, putting them back into the backlog or another sprint. Not new issues (unless you are adding them to the sprint and then removing them)
-
Boards are not containers for issues, they are a view of them. You do not "create an issue in a board". You create an issue in a project. If it appears on a board when it is created, that is because the board is set up to select that issue. Typically, a new issue in a project will go into a backlog, not a sprint (current…
-
It's in the sprint report, as mentioned in the question.
-
Yup, my pub fed me that one a while ago. Quite fond of the Monkey Shoulder as well.
-
There are only three reasons a log will not show you an error: * The whole server is stopped (pulled power cable, hard reset, hardware fault). * The Operating System or user kills the process for some reason. * You've turned off all the logging. If your Jira is stopping for any other reason, there will always be…