-
Adjust the text colours for the 'Info about this merge panel'
Adjust the text colours for the 'Info about this merge' panel
See the bottom of this screenshot for the example: https://gyazo.com/a57c98b8ad7b39f4b76e8371a6900c15
3 votes -
Add suggested corrections to spell checking
Spell checking should suggest corrections via the context menu and not only underline mistakes. Many people may be fine with the visual hint, but there are quite a lot of developers who have trouble with spelling, especially in foreign languages, and would benefit from corrections.
As an aside, I would also welcome a Grammarly plugin like in Microsoft Word or browsers nowadays.
5 votes -
2FA and IP Whitelisting for Cloud
For security purposes, it would be nice to be able to have extra security when logging in or to verify who has access to the repository. Something similar to what Bitbucket or Github Implement would be nice.
9 votes -
Jira Next-Gen project integration
Plastic integration with Jira Next-Gen projects is broken. There is no way to send data back to Jira projects from Plastic. There should be a Jira plug-in to make the set up for this not only possible but easy.
6 votes -
Correct bacwards searching
Hello.
I probably discovered following error: When searching for given word within changeset diff, the backward jumping does not operate -- pressing "search previous match" button has no effect whereas "search following match" have.
Regards
Jiri Kohutka1 vote -
Add a "Check for updates" button in the About panel, so I can see if I'm on an old revision.
I just want a button next to the version number that shows me what the latest version is, and downloads it if want to upgrade.
16 votes -
In Changesets view, also show files in change set
In the Changesets view, have a split view, that shows the filenames of the files in that change set.
The view could be just like you use in the Pending Changes view, where the split is resizable, with the top half showing change sets, and the bottom showing the files in the changeset currently selected. That way you can quickly arrow up/down through the change sets and see the files instantly in that set.
If you want to get to the diffing tool, you still need to double click the changeset. This is only about showing the files in the…
9 votes -
6 votes
-
More details on merge conflicts
I'm new to Plastic, and just had my first merge conflict to address.
I think on this screen, where you choose between Source/Base/Destination, it would be really helpful to show the username, checkin comment and timestamp associated with Source and Base, as a helpful peace-of-mind, 'I am not about to accidently break the build' feature.
I ended up tabbing to the Branch Explorer and using the Changeset numbers to look up these details, but it felt pretty fiddly to do.
1 vote -
Default changeset query for xlinks is weirdly narrow
When adding a new xlink to a project, you must select a target changeset to track on the linked repository. When you open the dialog box, the default search query is this:
find changeset where date > '5/27/2020' on repository '<repo_name>@<server_name>:<port>
(today is 6/26/2020)
For some reason it always defaults to only show changesets from less than 1 month in the past. Seeing as xlink is primarily used for reusable, modular code, this means there is almost never any changesets shown. So in order to find the latest changeset you have to click "Advanced" and remove the date clause manually.
…
1 vote -
Option to revert pending changes when switching workspace
When trying to switch the workspace to a different changeset/branch, the user is first asked if he's sure, but then gets an error if there are pending changes.
It would be great if the question dialog would show how many pending changes there are (and maybe a tooltip with a list of all changed files?). Then, if the user decides to go through with it anyway, the pending changes should be reverted (maybe have a checkbox, so the user is really sure) and the switch should be performed.
When there are no pending charges, the switch should just happen without…
6 votes -
Better handling of dark theme in Linux
Using a dark theme with the linux build ends up with some pretty glaring white backdrops to things and lots of unreadable text.
It seems Plastic isn't using the supplied gtk theme colours, but instead has hardcoded colours for certain things.
12 votes -
"Add existing workspace" button
On the workspaces tab, next to "Create new workspace..." a button "Add existing workspace" would be amazing.
Use case: I recently received a new laptop and all of my working files were copied from my old laptop including a folder containing numerous workspaces that are >10gb each, I needed to work on some of these projects while out of the office but couldn't find an easy way to add them back in to Plastic and recreating/downloading them from scratch while remote wasn't an option.
10 votes -
Implement cloud-based backups for Plastic Cloud
I propose that Plastic Cloud offers an incremental backup method. It should export backup data to customer-provided cloud storage (AWS S3 / Google Cloud Storage / Azure Storage), perform backups with high frequency (possibly with a combination of full / incremental backups), and only leave the responsibility of validating these backups with the customer.
Our use case:
We use Plastic Cloud instead of Plastic Server, because it reduces our operational overhead. Plastic Cloud is great in many ways, but using it means that we also entrust the responsibility of availability, security, as well as backups/disaster recovery with Codice Software.
As…
13 votes -
Using GMaster: Would like to wrap text in Difference window
I am confused: Is GMaster a subproduct of Plastic SCM ???
1 vote -
Don't create empty commits in xlink upon merge-to
If I complete these steps:
1. Create repos B and A
2. Commit file foo to repo B (this becomes cs1)
3. Create xlink /b in repo A as -> cs1@/main@B (writable)
4. Create branch /main/task001@A
5. Checkin several files without touching /bI can then complete my task branch like this:
6. Switch workspace to /main@A
7. Merge from /main/task001After this, B will still have only one branch and one changeset, because no changes were made inside of /b. Wonderful!
Alternately, I can complete my task branch like this:
6. Merge-To from /main/task001 into /main@AThis is a…
3 votes -
Add "Merge Query Rule" to conditional format
In the Plastic GUI, "Add format" provides the following options:
- Branches with pending merges
- Active branch in this workspace
- Custom branch query rule
- Custom changeset query rule
- Custom label query rule
cm find, however, supports additional objects beyond "branch", "changeset", and "query". I would like to highlight changesets that contain merge-links from a specific branch, but currently the only way for me to do that is to run the query in the command-line, use the query results to apply attributes, and then use the attributes for a rule that colors the changeset. It would be more straightforward if I could…
2 votes -
Support Multiple Search Terms in Workspace Explorer
Searching in Visual Studio allows me to set multiple search terms separated by a space in order to better narrow my results. This is helpful if you aren't sure if the name of the file is "ProjectXMLData" or "ProjectDataXML", but you know for sure it has Project and XML in the name.
Attached Images
- VSSearch01 - Shows searching for all 'project'
- VSSearch02 - Shows adding 'xml', but not as an exact match. The results are still displayed as expected
- WSSearch01 - Shows searching for 'project' and results show as expected
-…9 votes -
Integrate git sync into sync view
I would like to be able to mirror a client's Git repository, create a new branch, and then pull changes from the Git repository without pushing my unfinished/proprietary/scratch/experimental branch.
I have also, from time to time, found myself wanting to clone just a single branch from Git, exclude some branches from Git, or pull everything without pushing anything. All of this is possible in Plastic sync view with Plastic repos, so I thought it would be better to suggest integrating the two instead of suggesting to add these features independently to git-sync.
2 votes -
Support wildcards in gitserver.conf's export.repo option
For example,
export.repo=foo
export.repo=bar
export.repo=git mirrors/*1 vote
- Don't see your idea?