Comments
-
This has nothing to do with the original question. Please have a look for the subject in the community and if you can't find anything that helps, raise a new question.
-
Only Epic type issues can have the Epic Name field, and you can only have one Epic type. Even if you could unlock the scheme (which you can not do on Cloud), adding the field would make no difference, as your issue type is not an Epic. There's no "workaround" - there's nothing to work around!
-
When Jira throws "An internal error has occurred.", it has written more detail into the logs (unless you've deliberately reduced the logging level in "logging and profiling". You will need to read the log to see what the real problem is - see <jira home>/logs/atlassian-jira.log
-
Have a run through https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-microsoft-internet-information-services-iis-833931378.html
-
Cloud is not going to get priority schemes apparently. Next-Gen projects may enable per-project priorities internally though.
-
Nope, that's a priority, not a severity. And you still have the problem that it is subjective and hence generally of no use. By all means capture your descriptions in a field, but do not call it "severity", because it's not.
-
You won't get another field to work like Epics directly, but to add to the other answers here, you could also look at Structure or Portfolio apps - Structure allows you to define more layers, and Portfolio directly implements features and initiatives.
-
I too would strongly recommend not equating story points with hours. They really are not intended for that. If you want to use hours for estimates, then don't bother with story points, just use the estimates directly.
-
You have broken your database, re-indexing won't help because it's just reading from broken data. Please, restore to the backup you took before running your SQL, it's the only way to safely fix this properly.
-
Only if you have the add-on that runs the scripts.
-
You need to add yourself to the space permissions, and then check the "page" column for a tick in the "delete" column within it.
-
Yes, you have entered the account credentials incorrectly too many times, so you now need to answer a Captcha to check you are not an attacking robot.
-
Yes, that will work fine. A more generic example would be * Field A - normal field * Field B - normal field * Field C - normal field * Field D - scripted field for A + B * Field E - scripted field for D + C Field E will fail randomly when A or B are entered or edited, because D could be calculated before or after E. So you…
-
You can't get the display you want, but you can search for "issues that will carry over". Have a look at the board config and check out what status are in the very last column. Now search for Sprint = <current sprint> and Status not in (<all status in last column>)
-
You will need to add code to that to search for a list of issues (ideally based on "project = XXX", to minimise the size of the search) and iterate over them, reading the custom field value for each one.
-
Yes, the macro is a bit weak, it does not take account of current page, or allow you to create from a named page. There are a couple of macros in the marketplace that do do this, although the only one I know of is part of ThemeBuilder called "create child" (it's mostly the same as the built in one, but asks for a page to…
-
>Documents that was on this page wasn't created in confluence. That's wrong. Documents on this page are links to Confluence pages and templates. I suggest you check the visibility and restrictions on the pages in Confluence.
-
Actually, it's completely the right behaviour to allow humans to use a system. It's a fundamental design flaw when systems fail to use terms their target audience do not understand. Failing to put a human-readable id like the space and page name in a url is just as dumb as assuming that we can remember a 15-digit credit…
-
This is not something I would try to do with an issue tracker such as JIra, it's not well-suited to it. If you are going to do it in Jira, could you describe what you have done so far, and how you would like to do more in the application?
-
No. An app is either installed (globally) or it is not. Some apps do support "only show in some projects", but that is entirely up to the app, not Jira.
-
Problem - this is only one way people might want to work. Please suggest how you will code for the other three ways I've seen people do it, and then allow for the ones I've not?
-
No,Jira issues are the core of everything it does. It's all tied to an issue.
-
There is no access to the logs on Cloud. If you have the admin audit log enabled, issue deletions are captured in there (they will tell you who, when and what was deleted), but that is your only option on Cloud,
-
You can't do this in general. Apps can add so many different functions, to so many different places, you don't stand a chance of doing it with SQL. And you can't answer "what plugin is used by what project" for many because they're not project apps. If an app adds a workflow function, yes you can scan the workflows for it,…
-
No, do not do that. That is exactly what I said you should not do. You're tossing a coin as to which script runs first. The script you've given here could return the wrong result if the progress field changes in the same change.
-
Yes, in the database, it use the AO tables to hold the scripts.
-
Dashboards do not have filters, gadgets do. You will need to edit each gadget on the dashboard to change its filter (if it is based on one). If you need help with that, see @John Funk 's answer!
-
You will need to explain this more - "mba stream" is not useful, and tell us what it has to do with Atlassian?
-
If an Atlassian account is being abusive, then yes, you can remove it from your instance as @Earl McCutcheon says, but there's no formal way to complain about the account to Atlassian. However, as the account can also be used here on the community, the rules here apply and we can get the abuse raised with Atlassian. If you…
-
Bear in mind that working hours can mean two different things. Service Desk working hours are the times that we tell people that service desk calls will be worked on (for example "if you raise an issue after 5pm, it may not be looked at until 9am the next day because our working hours are 9-to-5). Core/Software working…