Comments
-
If you want them to see the issue after the move, you have to give them access to the new project.
-
Create a new workflow scheme (or find one that is right already) that maps the workflow(s) you want to the issue type(s) in the project. Then go to the project admin and swap to the new workflow scheme. That de-simplifies the workflow. However, you say "I need some other status" - when you created them, do you map them…
-
See https://www.atlassian.com/licensing/cloud#monthlypricing-1 and then log into your atlassian account where quotes can be generated.
-
There's nothing you can do with "service desk is slow". When something is slow, you need to look at where and why. "It's slow" is useless as a diagnostic, you need to look at what is slow. Start by working out if it's the server, the network or the client. Or a combination. You need to measure. What does "slow" mean to…
-
Yes, there's no Jira data in the Confluence database, it's pulling the data over the REST api when it needs it. Your add-on suggestion does the same, but via a direct database link.
-
No. If you delete inactive users, you could damage or destroy the history of your system. In general you should ignore inactive users, not delete them. They don't count towards your licence, can't log in, and can't be added to issues (but they can still be searched) NEVER delete them from the database, you will do all…
-
You can't. The second half of your requirement is nonsense, as you can't select things that are not there. The Jira issues are in the Jira database.
-
Start at https://confluence.atlassian.com/servicedeskcloud/receiving-requests-by-email-747602718.html
-
It varies between each and every add-on. ScriptRunner, in more recent versions, has the "script registry", a long list of all the scripts you've got in one place. That can help with identifying where SR has been used, but still won't give you a direct answer, because it can't
-
You can't change localhost (well, you can, but that way lies madness). Localhost should always point to 127.0.0.1 and/or ::1 You need to look at the external ip address of your Bamboo machine, the one that connects it to your network. Try ip or ipconfig to find out what it is. What happens if you telnet <external address>…
-
It does sound like you are looking at two different fields. "Components" is a system field, but you've said your data is in "Associated project components", so you should be reporting on that, not components.
-
You will need to look at every add-on, work out the list of functions it provides and then go over the config of every project to see if they use it. You will find there are some that you simply cannot tell. There is no quick way to do this, as add-ons can add so many different functions and the way to "see if it is used…
-
If you're counting, will there be extra points for alliterative attempts? e.g. would "Agile AMA" count twice?
-
You will need to find or write an add-on that provides a new email handler, one that can recognise and process the remote system's key. Jira can only work with its own keys, it can't understand some other system's arbitrary keys. The other option is change the way your helpdesk works so that it includes the Jira issue key…
-
Versions are project level item, not global. You can use versions of the same name in different projects, but they will remain separate objects. Portfolio has some functions for handling global releases.
-
See https://confluence.atlassian.com/get-started-with-jira-service-desk/make-queues-for-your-team-917968317.html
-
The "solved" flag is for "there's an answer that tells us nothing else needs doing". Mostly that means that the original question has an answer, but it can also mean "closed because there is no answer", or, as in this case, "closed because there's an issue which tells you the state of the request"
-
Start at https://developer.atlassian.com/server/jira/platform/creating-a-project-template/
-
That suggests your proxy is not directing the data correctly then. The body of the request looks like it is being remapped somewhere, to the old url with 8080 in it
-
Yes, depending on the version of Jira. Check the "supported platforms" documentation for whichever version(s) of Jira you are looking to install and use.
-
If/then are another way to express the logic, they don't do much different. A set of conditions should lead you to a simple boolean true or false. You can express them as if/then, or as and/or statements or a mix when you're coding, but for conditions in Jira transitions, you have to use and/or. Look at the second layers…
-
See https://confluence.atlassian.com/servicedeskserver/managing-the-email-channel-939926306.html
-
You don't give it a url, just select a page in the current space you want to use as the home page. Most of the space blueprints create a home page automatically.
-
Mail handlers are for Jira Core or Jira Software, Service Desk does it differently. Are you interested in Service Desk or non Service Desk?
-
See my previous comment for how issues are "done" And you do need the resolution field.
-
Best practice is to go with the software as it is intended to be used. You need to fill the resolution field appropriately as a good swathe of Jira needs it for reporting and statistics, irrespective of what you do in Scrum. "Do not need the resolution field" is wrong when talking about Jira, you need it, whether your…
-
The Scrum and Kanban boards use different criteria - scrum is the column on the far right, Kanban uses a non-empty fix version to say "done". However, if you look at the issues in any other way than the actual boards (including some of their reporting), the resolution still matters.
-
I suspect it's because your nesting is not doing anything. At the top level, you have two condition groups joined. The first group says "The field fixed in svn version # ... equal to null". The second says "The field fixed in svn version # ... not equal to null". As the join is "any", then you are going to find that every…
-
No. If you remove an issue type from a scheme, you have to swap all issues using it to an existing value. There are some hacks and tricks you can play removing it from drop-downs, but they're easy to bypass and only work in some places. A user will always be able to get around them quite easily (and sometimes purely by…
-
I suspect you need to add the client certificate to Jira and subversion so they can talk to each other over https.