Bug 383687

Summary:	Adding newly imported projects to the build sequence: consider making it optional
Product:	[Applications] kdevelop	Reporter:	RJVB <rjvbertin>
Component:	UI: general	Assignee:	kdevelop-bugs-null
Status:	REPORTED ---
Severity:	wishlist
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	All
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description RJVB 2017-08-19 09:11:05 UTC

While my multi-project sessions usually contain related projects it is extremely rare that I have any use for the build sequence feature. If anything it would require me to install through the IDE, which is something I'm very unlikely to consider doing.
It's also a pure coincidence if I import projects in the exact order of dependencies (if anything it's usually the reverse order).

Having projects declared in the build sequence thus interferes with building, and I've made it a habit to remove each newly imported project from the build sequence.

That's 2 unnecessary clicks that are beginning to grow old on me, so I'd like to suggest considering a global option to disable the automatic adding of new projects to the build sequence. Adding them manually also takes 2 clicks.