On Roadmap - How to make issue colour not linked to epic colour?

[Mark McCarrick]

Hello, I'm trying to configure settings which will show on the roadmap, issues by their set colour type and not inherit their epic colour which they sit in.

At the moment, I can change the epic colour and it will change all child linked issues colours to the same. This is irrelevant if the issue colour is set to something different.

I can change the epic colour by right-clicking and this will change all the issues underneath. 

I can't change the issue colour by right-clicking on the schedule:

At a glance, I want to be able to group issues using colour. So the epic can be whatever colour, in this example purple. But I want the issue colours to show as yellow and keep the epic colour the same as it was.

Hope this makes sense!  Can anyone help advise?

Thanks!

[Bastian Stehmann · Accepted solution]

Hi @Andreas Moormann,

Jira stores the data in a database. Passwords for example are encrypted, content for issues is not encrypted. Attachments are stored in the filesystem, they are also not encrypted.

[Nic Brough -Adaptavist-]

Actually, passwords are not encrypted, they're salted and hashed, but that's a technical quibble.

It is possible to use encrypted databases and file-systems, but the software itself does not do it, it relies on the database and operating system to do the work when you need it.

[Andreas Moormann]

Hi @Bastian Stehmann, @Nic Brough -Adaptavist-

Thank you both for the clarification!

[Justin Wilson]

In case you need a more fortified solution, 

We are an Atlassian Solution Partner and had a lot of requests to strongly protect specific data (file attachments or extra-sensitive fields) and limit access to specific groups/individuals.

As of July 2020, Team Secrets is the only add-on which can also handle Service Desk portal request screen attachments & encrypt them with 2FA in this way (new functionality) - please check it out if it suits your organization's needs

https://marketplace.atlassian.com/apps/1216894/encryption-security-2fa-for-jira?hosting=server&tab=overview

[Yannic De Baets]

Hello Justin,

Seems like a good solution, but i have a question: can you also edit a "secret" that was saved/published before, so do a edit or update of the saved/published secret? (after testing your solution, i'm not sure that is available, hence my question).

Thanks for your info,

Regards, Yannic

[Justin Wilson]

Hello Yannic, 

Not at the moment, though this is on our roadmap.

We support two types of "secrets": files & text. 

Editing doesn't seem to make sense with encrypted files as you'd simply upload a new replacement files since graphic, video, or office document formats cannot be directly edited in Jira. If there is an interesting use case for editing though, we'd love to know about it. 

For secure text fields, it does make sense since you'd directly modify the text in Jira and save the changes.

We're planning to first add support to edit ownership and share settings. Second we'll add support for direct secure text edits. 

Regards. 

[Dan Ivory]

Hi @Andreas Moormann,

Perhaps a bit late to this, but our app Encryption for Jira should help you if you need to encrypt attachments and text fields (using E4J's Encrypted Custom Field). This will encrypt your data in your database and file-system.

Hope that helps,

Dan

[Yannic De Baets]

Hello Dan, 

Is this solution also available for Jira Cloud (or is it not neede there since all is already encrypted)?

Thanks for your info,

Yannic