Comments
-
It might well be only one line, that makes it easier, but I'm explicitly asking to look at the history of the issue, as shown on the history tab. Not the transitions tab - it's useful, but not for working out what has happened here. The transitions tab has headings like Transition, Time in source status, execution times,…
-
That doesn't look like the history tab, more the transitions tab. Could you look at the history of the issue?
-
So it's not closed any more. It doesn't matter if you think you closed it - it's clearly saying it's in an open status and is unresolved. Could you look carefully at the history of the issue to see what has been done to it - obviously pay close attention to the change of status and resolution. Could you also check the…
-
You will need to explain this in more detail. What do the status and resolution fields say when you view the issue? What do you mean "cannot close" - no option? Error when you try it?
-
Thing is, it's NOT a link, it's a block of text that you want to format differently to other blocks of text. Have another look at the user macros - you can use them to wrap formatting around blocks of text. Not the existing ones, but writing one for yourself - https://confluence.atlassian.com/display/DOC/Writing+User+Macros
-
That's because it's not really a proper http based url, so Confluence can't understand it as a link. I don't think you can do this without some code to tell Confluence "this is a non-standard link, please treat it the same way as an http url". I'd try doing that in a user macro though - I have seen this done before, but…
-
How have you "mapped" the NAS drive? Backups can be done to shared storage (although latency and potential disconnects mean it is not a recommended or supported thing to do in most cases), but there are some quirks, and Confluence will not recognise some types. We don't even know what OS you are on, let alone the mapping…
-
You don't seem to have removed anything from that file. But assuming I'm misunderstanding and you have edited something...Have you done both files? HTML and Text? And restarted JIRA?
-
Yay! Glad it worked in the end!I do find trying to comment velocity a bit of a pain sometimes - sticking the ## on the front does work, but I forget that it makes it harder to follow properly.
-
That line is trying to parse (include) another .vm. If you give it a non-existent file, it's going to fail. My suggestion was that you comment or remove that line, so I'm not sure what you're doing there. The previous comment also seems to have some output that implies you have not removed/commented all of the lines I…
-
The 2nd to 6th lines
-
The code in the .vm files is pretty simple to read and amend, especially if you're just for removing comments - the code is not far off "#if (comments exist) show comments #end". Open them up and have a look, it's quite easy to read, as the templates are not complex (compared with the reporting ones, or things that have…
-
That's all to do with the file system operations and permissions, it's not something Jira or Confluence will handle for you (the installation will follow whatever the defaults are on the server) To prevent it happening again, you'll need to work out what the settings are on the file system and change them to something more…
-
We are a community of end users, NOT Atlassian. You really MUST raise this with Atlassian directly. You've got the right email address to contact them (sales@), but keep trying. You might also want to raise a p1 in their support desk for OnDemand.
-
It usually means someone has moved the issue from "open" to "in progress", but customised workflows can use it on any transition. I'd try not to put it on any transition that does not sound right for the name. It's no different from any other event - a notification will be sent if you've configured your notifications to…
-
It's restricted - see http://confluence.atlassian.com/display/AOD/Restricted+Functions+in+Atlassian+OnDemand and then raise an issue with support to get your data imported.
-
Closed, because 1. We have no idea what you are talking about - you've posted a new question, and I think you should have posted against an existing conversation 2. Support issues on Atlassian's site are only visible to the Reporter, Atlassian, and people added by Atlassian or the Reporter. Most of us can't see the…
-
You don't need to. If you have JIRA or JIRA + Agile, you will be moved to JIRA Software automatically. If you only want JIRA Core (i.e to lose the Agile bits), there should be an option to do just that (I understand it's not too clear where, but if you get stuck, contact Atlassian sales or support) If you need a new…
-
Resolutions are a global list. >I want to get all the resolutions of an issue That's nonsense, as an issue is either unresolved (no resolution) or resolved, with $issue.getResolution() returning the resolution.
-
You don't need code. Look at Admin -> Issues -> Resolutions. Or just go visit an issue that is ready to be closed and has a resolution field on the close screen - the drop-down lists the options (although some people do customise that list, so the better option is the one above) If that doesn't answer the question, you'll…
-
No. To enable it when you've got no subtasks, you need to hack the core code in JIRA to suppress the code that says "if sub task count < 1, don't display panel". I think it's in a template somewhere, rather than JIRA java code, but I'm not sure. On Cloud, you have no access to the installation to make changes like that.…
-
Make sure you have "delete" rights in the project, and the global permission to use bulk-edit
-
No, I think you've missed the point. 1. No, as I said, You have different workflows for different issues. 2. No, as I said, different workflows can have different sets of validators (and conditions, status, transitions, post functions etc) 3. Create a workflow called Bug-wf. Create another workflow called Issue-wf. Use…
-
Three options 1. Define different workflows for the different issue types (bug workflow has the validators, story workflow has different ones) 2. Write new validators that include "if issue type = X, then <rest of validator>" code
-
Yes, there's a lot of caching, that's why you need to stop and start it. A background re-index does not delete everything and start again, unlike the full one. A project index is similar to the background one - it might fix it all, but you really should be doing a complete one.
-
Arg. Never touch a Jira database when it's running. Generally, 99% of people who try it even when it's not running shouldn't have because they don't understand it well enough. Try the following, and then consider restoring from the backup you should have taken before running the SQL. 1. Stop Jira 2. Check that the database…
-
I assume you've checked the marketplace for add-ons and found none? If that's true, then you'll need to have a look at a bit of coding - if you can get Appium to make REST calls to JIRA, then you can easily do this sort of thing - JIRA's REST interface allows for creation and updates of issues remotely.
-
No, it's not. The notification schemes send to everyone nominated in them. All you can really do here is make the scheme as quiet as possible. Avoid the use of groups and keep the roles down to a minumum You might also want to check people's account settings - the "do NOT email me on my own changes" flag is very useful
-
It might be in the registry, but Java is system independent and doesn't care about the registry unless you specifically code to read it. It only reads the environment (which is partly generated from the registry on windows boxes, but often badly or not at all) Go into your Jira/Confluence/Whatever "system information" page…
-
No, you can't hide a status at all. Even if you did something clever to remove the field from all viewing when it's in a status, the partner would still note that there's an empty space where it should be, and hence deduce what's happening. You could hide the issues that are in a status by setting a security level as the…